Hi Marek,
interesting... For Surefire 3.0 we have some stuff in mind to allow users
hooking in the surefire logic at several points, one of them being the
determination of tests to run and their execution order. I didn't think
about that particular case of yours, yet. But good to know.
As for
I’ve got it somewhat working by extending TestsToRun with my implementation.
Everything is fine, except that surefire loads all test classes before
launching any test just to create test description.
(It’s a JUnit4Provider that’s doing it).
Do you think it’s safe to omit creation of test
