Hi Dan,
I did it this way so that JUnit suites and standalone tests can share
initialization code for running under the old test harness. There are
other solutions to the problem: the shared code could go into a separate
helper class or be factored into a superclass of DerbyJUnit. Each of
these solutions is awkward in its own way. The solution I adopted seemed
simplest to me, but, as you said, it raises this question of whether a
set of tests should be considered to be a test itself.
Regards,
-Rick
Daniel John Debrunner wrote:
Daniel John Debrunner wrote:
LangSuite extends DerbyJUnitTest, but it's not a test it's a suite, is
this a requirement of Junit?
Any answer to this one? In my mind a suite is a set of tests, not a test
so it should not inherit from DerbyJUnitTest.
Dan.
