Change Notes item #684868, was opened at 2003-02-11 19:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=381174&aid=684868&group_id=22866
Category: Build System Group: v4.0 Status: Open Priority: 5 Submitted By: David Jencks (d_jencks) Assigned to: David Jencks (d_jencks) Summary: Per module test target Initial Comment: Prompted by extreme need, I've added per-module unit tests to the jboss 4 build system. Put your test classes in src/test/<same package as the class they test> They will be compiled to output/test and output/get/test To use, add this to your module build file, right before the output (jar) target: <target name="tests" depends="_default:tests"/> To run, ./build.sh tests or ./build.sh tests -Dtest.pattern=**/MyOwnUnitTestCase* to match just some tests. I'm using this for the common and system modules. I suggest we use these module test targets for real unit tests of anything that doesn't need all of JBoss running. For instance, I have several tests of ServiceController etc that only require an mbean server to be started. TODO: collect all the results together with the main testsuite for the test report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=381174&aid=684868&group_id=22866 ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
