They'd probably solve the problem of 7 minutes to build to run a single test that I experience.
Moving stuff to module specific test dirs would be a lot of work. I wonder if instead we could make dir-specific generic build targets -- something like in ${test.module} run xdoclet, compile all classes, then run jar for ${test.module}, then run tests in that module also. Sort of like "test" but limiting the xdoclet and jar tasks also. The build file is getting so large this might help make it more comprehensible also. david jencks On 2002.09.19 17:36:29 -0400 Scott M Stark wrote: > > I don't really see how module local tests are any improvement over the > test and > one-test targets in the existing testsuite module. In some ways it is a > problem > because now you have additional dependencies to build and run the tests > in > the module. > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > > ----- Original Message ----- > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, September 18, 2002 10:29 PM > Subject: RE: [JBoss-dev] Build System... any ideas > > > > David and I talked about this on the way back from Tahoe. I would like > > to revisit the entire TestSuite, putting a testsuite in each module, > > which would perform Unit tests for components and parts of components > > for that module alone. Then the jboss/testsuite would be an > integration > > testsuite. > > > > This way, if you are working on bits from the cluster module, you can > > write simple tests to validate your component and run the tests > quickly. > > Then when you are satisfied, you can write an integration test, which > > would actual test a real component inside of a JBoss instance. > > > > This will get us more coverage, but will also encourage developers to > > make smaller, simpler tests for stuff and make it more likely they will > > run them, as it won't take forever. > > > > Also, on the subject of build systems and testsuites, I have been > toying > > with the idea of allow Java and Jython tests to be run together. Using > > Jython it will be faster to throw together small and functional tests > > with much less code and a lot less trouble. We would still need Java > > tests to run stuff that is type dependant, but the two could live > > together happy. > > > > The build system overhaul is a dependency of this I believe. > > > > I have been planning on doing all of the above... just I haven't had > the > > time to make any progress. Also I really want to finish the basic > > command line console framework. > > > > Fuck, I need my boss to stop making me work on their lame ass projects. > > Who cares about that shit really... bah! > > > > --jason > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development