Hi, in case you haven't read yesterdays commit message, here is a quick heads-up and request-for-comments.
I've added a forkstyle="once|perTest|perBatch" attribute to <junit> that gives more control over VM creation in forked <junit> tests. The old behavior is to fork a new VM for each test-class, this is what perTest does and it remains the default. The two alternatives now are to fork a single VM for all test classes[1] or for each <batchtest> set of classes (the tests given as <test> elements form a logical batch here as well). Gump runs quite a few forked junit tests and things went well, so it looks as if I haven't broken anything. Before I start to write the docs for it, I'd like some feedback on the name of the attribute as well as its current values. You know, I have a track record of choosing bad names. 8-) Stefan Footnotes: [1] Actually for all tests that have the same configuration of filtertrace, haltonfailure and so on. So it may be more than one forked VM in the end. -- http://stefanbodewig.blogger.de/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
