An alternative to your approach is to explicitly use <test>I do realize I have this option, but then I'd have to hardcode the
elements for the tests that need a certain order and exclude them
from the <batchtest> that contains the rest.
test order in build.xml.
But only for the few files that would fail quickly - or alternatively
for the few files that run really really long (put the single <test>s
after the <batchtest>).
You could also have different class names for the tests you want to run first. Then your test target would be comprised of two depends: one for thequick tests and the other for everything else.
Not ideal.
L
-- <Laurent Duperval> [EMAIL PROTECTED]
"For every bug fixed, there is a bigger bug not yet discovered."
