Does anyone have an opinion about where JUnit tests should be stored
under enhanced/classlib/trunk/ ? These will be new tests for bug fixes etc.
The current layout looks like this, with a couple of options marked:
enhanced/classlib/trunk/
depends/ <- 3rd-party stuff + some resources
doc/ <- doxygen output
java-src/
archive/
src/ <- java code for archive component
<<option-1>>
native-src/
linux.IA32/ <- linux native code
win.IA32/ <- windows native code
<<option-2>>
I don't have a strong feeling either way.
<<option-1>> says put the unit tests into a folder alongside the
implementation of each component of the class library (archive, math,
etc.) That way the tests live with the implementation, and there is a
good incentive for the two to be maintained simultaneously. It does,
however, make the packaging a bit more interesting because the tests
have to be separated -- this is not a big deal though.
<<option-2>> says put the tests into a parallel hierarchy at the same
level as the java and native code, e.g.
.../trunk/java-tests/archive/src/ and so on. This makes the packaging
of the tests simpler since they are out of the way and allows us to
treat them as separate components.
FWIW: I see that the HARMONY-16 contribution has the equivalent of
<<option-2>>.
Thoughts?
Tim
--
Tim Ellison ([EMAIL PROTECTED])
IBM Java technology centre, UK.
