DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch ------- Additional Comments From [EMAIL PROTECTED] 2003-07-15 16:52 ------- Are we talking about my DynamicTestSuite which would do introspection on the test cases to look for public static final Strings, and decide which tests to run based on the values? It did indeed bunch up all test method, although It's mostly an Ant reporting artifact, since using normal JUnit test composition. To get the nice hierarchical reporting, we've since switched to a file selector that performs similar checks on public static final Strings used a dedicated little class parser (BCEL would work fine as well of course). Using fork=true is really expensive when tests depend on services to be started so they can run, which adds up to the VM startup time. What a colleage suggested to me was to have the ability to define several groups of tests to run each (the group) in a separate VM. Sounds like it could be achieved with an additional attribute (like groupFork="true"), and make each different fileset of the <batchtest> be a separate group. Using our custom selector to kind these fileset groups thanks to new String would be trivial. I'm just muttering. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
