While Dries is away, and at least before the DrupalCon (and its awesome Testing Party!), we really should clean-up the Simpletest module and core tests.
Here is a battle plan:
- First, we need to agree on and document a naming convention for test files (name and directory), and for test classes; this should probably go in the handbook;
- We need to find a definite solution for hook tests (http://drupal.org/node/268063);
- We need to document usual "test patterns" that we use in core tests (doing the opposite of http://drupal.org/node/30023: document how to do something using methods and assertions from DrupalWebTestCase);
- We need to clean-up tests themselves, to ensure both clean coding style and consistency in the use of testing patterns;
- Lastly, we need to battle the last fights for having a 100% pass rate (at this time: Cache expire test, Core filters, String translate and Poll create are known to fail).
Hands-on, testing brigade! That's the last stretch home!
This is a wiki page, so please feel free to update it and link to the exact issues if they already exist.