Re: [Junit-devel] structure of test invocation

[Vladimir B. <vla...@bo...>]

> Which will be a suite of tests but not a TestSuite.   Which suggests 
> that maybe TestSuite should be an interface, not a class.


As long as you let the user decide _how_ the tests are executed you may 
not have any control on the execution.  If TestSuite is an interface, it 
doesn't solve the problem since you can still define your sprecific 
class (that implements TestSuiteInterface) that doesn't rely on any 
other object to execute the tests.

But what is the difference between a TestSuite and a suite of tests?  In 
the tree hierarchy that is created by JUnit, the TestSuite objects are 
the nodes of the tree, the TestCase are the leaves.

Can you propose some solution that will not break each and every test 
already written?  Maybe we're not in sync because we focus on two 
different problems.

-Vladimir

-- 
Vladimir Bossicard
www.bossicard.com