Posted by moshe weitzman on September 25, 2009 at 5:16pm
| Project: | SimpleTest |
| Version: | 7.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | boombatower |
| Status: | closed (fixed) |
Issue Summary
I am seeing table cleanup even when thats not requested as per admin/build/testing/settings. can anyone else get the tables to stick around?
Comments
#1
We had this discussion in core. The variable is not intended to leave the simpletest3948... tables...it leaves the "results" as in those in the simpletest table. The idea being that modules like PIFR or other integrations may want to do further analysis or work with the data.
If we want to provide another variable to leave tables...or change the meaning of this one that is a possibility, but not the purpose of the variable.
Personally I never have a need to look at the tables...at least not something that can't be figured out with debug() or verbose and dumbing things out. If you need to though: inside DrupalWebTestCase::tearDown() comment out line 1256
<?phpdb_drop_table($ret, $name);
?>
and the tables will be there for you to inspect.
#2
Lets add this, why not right?
#3
#4
Committed.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.