Core patches need to update tests as well

The current plan is for SimpleTest to become part of core in the near future. Once this happens the tests will need to be updated with patches to core. However, at this point SimpleTest is not part of core and whenever core changes break the tests someone, usually me, has to go through and figure out why they broke, make sure that the code they test doesn't actually have a bug, and fix them.

As we draw nearer to the Unit Testing Sprint we are attempting to plan and prepare for the sprint. Having to go through and fix tests whenever the core is changed can be quite time consuming. It would be helpful if we could begin the practice of updating tests along with the core before SimpleTest is officially part of core. Any help in this department would be much appreciated.

Recently a number of the tests broke due to changes in the core. If you would like to help please see the list of tests that should pass and make sure that they still do. Specifically, it appears that commit #109998 has broken over four of the tests and it would be appreciated if others could take the initiative and fix those tests.

Thanks in advance.

Comments

Right now, if we're to fix both core and tests against core, we have to both update the core code and run a (cvs) diff against that. Then we have to update contrib code and run (cvs) diff against that. This results in two patches that have to be evaluated and kept up-to-date etc. As soon as SimpleTest is in core, we'll have to run (cvs) diff just once and end up with just one patch to upload, have evaluated, and maintain. I know this is what has kept me from writing the tests for drupal_truncate_chars()...

I realize that it will be much easier once SimpleTest is in core and that is why it needs to get in core if Drupal is to have full test coverage, but at the moment it would be very helpful if the others could help maintain them and get into the habit of fixing the tests.