You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Curren (JIRA)" <ji...@codehaus.org> on 2009/11/10 07:29:55 UTC
[jira] Created: (SUREFIRE-580) Allow "fail fast" or stop running on
first failure
Allow "fail fast" or stop running on first failure
--------------------------------------------------
Key: SUREFIRE-580
URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (SUREFIRE-580) Allow "fail fast" or
stop running on first failure
Posted by "Deejay (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281429#comment-281429 ]
Deejay edited comment on SUREFIRE-580 at 10/17/11 6:16 AM:
-----------------------------------------------------------
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.
was (Author: deejay):
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 ammount of time wasted by our Jenkins instance to alert us to the fact that someone made a typo.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-580) Allow "fail fast" or stop running
on first failure
Posted by "Deejay (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281429#comment-281429 ]
Deejay commented on SUREFIRE-580:
---------------------------------
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 ammount of time wasted by our Jenkins instance to alert us to the fact that someone made a typo.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-580) Allow "fail fast" or stop running on first
failure
Posted by "Tomislav Nakic-Alfirevic (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309395#comment-309395 ]
Tomislav Nakic-Alfirevic commented on SUREFIRE-580:
---------------------------------------------------
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...
> 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
[jira] (SUREFIRE-580) Allow "fail fast" or stop running on first
failure
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306930#comment-306930 ]
Kristian Rosenvold commented on SUREFIRE-580:
---------------------------------------------
Could probably be hooked up to the maven "-ff" option if someone is willing to make the patch
> 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
[jira] (SUREFIRE-580) Allow "fail fast" or stop running on first
failure
Posted by "Tomislav Nakic-Alfirevic (JIRA)" <ji...@codehaus.org>.
[ 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