> BaseTest.setUp shouldn't mess
> with the suite method.
Ah ha. I had been thinking the same thing, but my tests were showing
just the opposite. However, after taking a fresh look at the code, I
found another stupid mistake; for no particular reason, I was doing:
suite.addTest(new BaseTest("testValidTest"));
suite.addTestSuite(Test1.class);
suite.addTestSuite(Test2.class)
So BaseTest.setUp was being called, but not for BaseTest.suite(), for
BaseTest.testValidTest. And then Turbine was staying inited for the rest
of the tests in the suite.
I was just lucky/stupid enough to have that testValidTest mixed in with
the BaseTest suite and have it first in the series of tests.
Everything works as per the TDK testing howto.
Thanks for the patience. I was too busy second guessing JUnit the entire
time to see the obvious answers right in front of me.
- Stephen
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
