[
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
