Selftest was a bit tangled up. This makes it clearer without any
functional changes:
* Use startTestRun and stopTestRun, as upstream python does
* lift test listing code out of 'TestRunner' into the DWIM layer
* push all test result outputting down into ExtendedTestResult rather
than being in the runner.
This means that the runner knows how to run, the DWIM layer knows when
to run, and Results know how to report on results.
Code-reviews will show the wrong diff though. Sorry - latency on trunk etc.
Selftest was a bit tangled up. This makes it clearer without any
functional changes:
* Use startTestRun and stopTestRun, as upstream python does
* lift test listing code out of 'TestRunner' into the DWIM layer
* push all test result outputting down into ExtendedTestResult rather
than being in the runner.
This means that the runner knows how to run, the DWIM layer knows when
to run, and Results know how to report on results.
Code-reviews will show the wrong diff though. Sorry - latency on trunk etc.
-Rob