The speedups aren't dramatic, especially after Robert worked on the longest tests, so this is not a huge priority.
Well, from time to time we try to clean up the tests... but i think it only takes a few weeks for us to 'lose' all the benefits.
I'm not trying to say our tests get crappier, a lot of the reasons for the slowdown is really just more test coverage...!
Basically, I don't think we can view speeding up slow tests as one-off tasks... its gotta be a continuous maintenance thing.
For this reason, its important to speed up the other parts of the build (like rebuilding jars over and over again
such as this issue), and also to integrate the nice random test framework work etc you did... these are more 'permanent'
However, I'm just concerned about adopting mike's cheating, because I like the idea of 'ant test' being a total pain
to catch broken stuff. New modules, etc are added often, the build system is refactored, dependencies upgraded, etc etc,
and I'm concerned we would somehow screw ourselves up and release stuff with bogus dependencies.