[
https://jira.codehaus.org/browse/SUREFIRE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306922#comment-306922
]
Tomislav Nakic-Alfirevic commented on SUREFIRE-580:
---------------------------------------------------
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.
> Allow "fail fast" or stop running on first failure
> --------------------------------------------------
>
> Key: SUREFIRE-580
> URL: https://jira.codehaus.org/browse/SUREFIRE-580
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Junit 4.x support
> Reporter: Paul Curren
>
> We have some slow Selenium builds. Waiting for indication of failure can take
> a long time. It would be helpful if there was an option to finish the test
> run on the first failure.
> We could configure this on some of our slower builds so improve the speed of
> the feedback loop in the cases where there are failures.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
