conflict between DrupalTestCase and DrupalWebTestCase [#287398]

In trying to run both contrib and core tests with 6.x I found a very odd and aggravating bug. If you run tests from (for example) CCK or admin_menu that use the 7.x API, followed by the poll module test (possibly others, but this is a clear example), then lots of the poll module tests fail AND at the end of the test Drupal acts as though simpletest and poll modules are disabled! One has to visit the modules page to get them to show up again!

This appears to be due to a stale list of enabled modules. In the poll tests, poll module was already enabled, so the calls to drupalModuleEnable() should have cause a message in the test report that the module was already enabled. This did no happen.

Comment	File	Size	Author
#3	wacky-router-287398-2.patch	681 bytes	pwolanin

Comments

Comment #1

yched commented 26 July 2008 at 13:22

could that be related to http://drupal.org/node/275052 ?

Comment #2

pwolanin commented 27 July 2008 at 01:06

Maybe related, but the fix that seems to work is to work is to reset the module cache in tearDown() - patch coming...

Comment #3

pwolanin commented 27 July 2008 at 14:39

Status:

Active

» Needs review

Status	File	Size
new	wacky-router-287398-2.patch	681 bytes

I'm having some trouble reproducing this on a more stock install - it's very odd and frustrating. Attached is the patch that fixes this when I see it.

note, this patch could potentially be combined with http://drupal.org/node/274486