I've seen horrified how latest version of Simpletest requires Drupal core patching to work.

Needing to keep a different copy of Drupal core for testing is at the very least annoying. This will also push back Simpletest usage for Drupal6 (do you want to patch your install to run tests for that small module patch you want to post?). On top of that, we are testing on a Different drupal than we are running which also can cause other issues (left over 'debug' calls in modules?)

I think at this point it should be more important to encourage and make easier adding and running Drupal 6 tests than adding any new feature to the module (whatever it is).

I'd really prefer keep running previous simpletest versions with my modules, though this will clash with other modules needing the latest one.

So please make everybody's life easier and encourage simpletest usage by rolling back these latest 'improvements'.

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (duplicate)

I'd rather keep the SimpleTests in sync and be able to have an even better SimpleTest in Drupal 6. Please check out the issue to get the patch into core so we don't have to patch: #582942: Add latest SimpleTest backport directly to core.

jose reyero’s picture

jose reyero commented

Agree that we should try to get that into core (Though it is certainly an API extension)

Disagree about making a new SimpleTest stable release before the patch gets into Drupal 6

And also disagree about this being a duplicate.

In the meanwhile, I'll keep using the old version of SimpleTest for the modules I'm maintaining...