I have been struggling with the test harness and want to propose some
changes. The things that are bothering me are:
1) It is currently impossible to run any of the integration tests (and I
believe some of the unit tests) by themselves. When I have lots of
debuggin turned on, it's a real pain to wade through the output of a
hundred tests in order to look at just one.
2) In the integration tests, I'm often not seeing the name of the test
in stack traces. I haven't figured this one out yet, but it makes it
really hard to figure out what test caused the problem.
I would like to go to a more 'standard' junit test harness where each
test can be run standalone. The usual way to do that is of course to
extend TestCase so that it sets up the test fixtures for the test, and
let the test extend the extended TestCase class. I don't see any
inherent technical problems with doing that.
In the most naive possible implementation the worst thing about this
approach would be allocating a new XmlDbClient for each test, hardly a
big deal when the time scale is being set by disk accesses.
Anyone have opinions on the subject?
If there's no major disagreement, I'd appreciate some help from Vladimir
(aka Dr. Test) on how to make these changes while taking advantage of
his junit addons in order to get guaranteed tearDown.
Regards,
Gary
