A quick correction on my previous note which reflects a bias towards the junit 3.8 approach that I didn't really intend.
some static code that performed any real startup overhead and cached the
helper. This all leads me to believing that to get true agnosticism wrt the test harness we should perhaps introduce bespoke function, some of which replicates the junit 4.1 features, either by creating an abstract specialization of TestCase or TestRunner or both.
We could of course introduce the generic test case behaviour for individual test method set-up independent of the junit TestCase class. Kelvin.
