Allow "fail fast" or stop running on first failure

I also require this feature. When using a combination of Spring and Liquibase, if the Spring config contains an error then on each and every test the Spring context will try once more to initialize itself, taking 20+ seconds each time.

This adds up to a huge amount of time wasted by our Jenkins instance to alert us to the fact that someone made a typo.

Same problem here: we use surefire + junit to run integration tests (maybe there is a better way, I don't know...) and our test suite takes hours to complete right now, yet most of the time we expect 100% correct execution and would like to know - as soon as possible - which test failed and why.

I half expect I'm using the wrong tool or using the tool wrong and one or more simple solutions are available. That said, I'm a bit puzzled that this issue remains open for three years: it seems to me enough to add a switch (e.g. -DfastFail=true, default=false) and wrap up test execution as soon as the first test fails, producing the usual test run output. Test methods which haven't been executed might have to be removed from internal data structures so that they do not appear in the reports.

Could probably be hooked up to the maven "-ff" option if someone is willing to make the patch

It would even be useful if test execution was not interrupted, but the result of each test be output after the test, not after the entire test suite. Something that would work like this:

$ mvn test | grep FAIL
SuiteA.test2 FAILED
SuiteA.test11 FAILED
SuiteB.test1 FAILED
[surefire still running]

I imagine that should be fairly easy to implement, yet it would still provide quick information about any test failures...