One of the hold ups for getting some momentum in the unit test process has been not quite knowing where to start. Part of the problem is that there has never been a easy place to see what needs to be done.

This has now been addressed with the Unit Testing Status page on the documentation wiki.

Manual attempts to get this page started haven't been all to successful, to today I wrote a program that creates it automatically. It identifies all the non-legacy classes in the "Joomla!" trunk, matches them against classes in the unit test tree, and produces a report.

There are three tables in the report. The first lists all the classes in alphabetical order, along with the number of test files for that class and the source file for the class. The second lists the same information organized by directory. The last table lists tests that aren't class-based, and tests for classes that don't exist.

The next job is to get rid of the sea of red (classes with no tests) on this report. There's a lot to do, but at least now it's easier to pick a place to start.