The Junit tooling is so useful I'd be loath to drop it as the harness that the Tuscany implementation uses for exercising the tests. I'm going to do a bit of playing to see what solutions are practical, but I'm concerned that we may be considering putting significant effort into a goal that's rather too theoretical, as junit seems so ubiquitous.
Regards, Kelvin. On 20/04/07, Andy Grove < [EMAIL PROTECTED]> wrote: <snip/> One option is to stop using junit completely and replicate the useful
features in a minimal test framework that supports parameterized tests e.g. we could introduce a CTSTestCase interface: <snip/>
