On 2001.11.19 16:35:48 -0500 Dain Sundstrom wrote: > Comments below (changed subject to reflect new discussion thread) > <snip> > Is this structure imposed by the build system or is it just a convention?
Looking more closely, anything named *UnitTestCase and not specifically excluded will be run in tests-unit. Put as many directories as you want in. > I > have a set of test that are based on the cmp 2 section "10.3.7 Assignment > rules for relationships" of the ejb 2.0 spec. There are test for each > relation type (1-n bi, 1-n uni, n-1 uni ...) and mapping style (fk, fk > with > back pointers, and relation-table). That is about 14 unit tests. Anyway > I > have these organized into sub-packages under the > org.jboss.test.relationship > package. I can't merge them all into package as each type has it's own > set > of 'A' / 'B' interfaces. Should I leave them organized into sub packages > or > should I eliminate the top level relationship package? > > The other issue I have is my tests use a, yet to be completed, extension > to > JUnit which runs the tests on the serverside (I wrote this). This is > required for testing local interfaces which by definition are not > accessible > remotely. Anyway, how do I go about adding the code to the build system. > It is in the package net.sourceforge.junitejb.* This is on sourceforge in its most recent state? I'd add the jar into thirdparty/junitejb/junitejb/lib/junitejb.jar with a readme saying what version it is. I'd think tagging cvs when you make the jar would be a very good idea. You might want to ask Jason first. david > > -dain > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
