Re: [dna] public testcases?

Hi,

From: "Ryan Hoegg" <[email protected]>

> For the loom configuration stuff using properties, I decided to go with
> a subclass of SAXConfigurationHandler.  In writing my test, I realized
> it would be nice to ensure that all the current SAXConfigurationHandler
> tests continued to pass after I override my methods.  Would you mind
> putting SAXConfigurationHandlerTestCase in src/java?

Personally I would not like to see any of our tests migrate across like
that. The main reason is that most of those tests are not designed to be
reused, nor are they stable. Between releases they could be completely
rewritten or whatever. In general most of the unit tests are whitebox tests.
If we had a consistent set of black box unit tests that we were willing to
support as a separate distribution then I would be happy to get that going.

Maybe the best way to see what we need is to have a look at your code and
unit tests. There may be another way to test the code that one of us could
pick up.

> I have needed to do this before in some of my projects.  I am beginning
> to think I want to create a sub-project of each project and put all the
> tests in there, using the reactor to run the tests in the sub-project.
> That allows me to have multiple projects sharing test code, and also
> allows me to have a different set of dependencies for my tests than for
> my main code.

For certain types of tests (blackbox, integration etc) this is the ideal
method IMHO.