[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285336#comment-285336 ]
Kristian Rosenvold commented on SUREFIRE-803: --------------------------------------------- The current failsafe verification could be modified to consider results for multiple executions. In 2.11 we actually already write a file that tells us how the build progressed (with runOrder=failedfirst or runOrder=balanced), and this would write a separate file for each execution. I suppose someone could write a patch that scans these files and make the verify phase in failsafe use these to evaluate if the build failed. There might be a few hoops to jump through regarding which files to read, but that should be solveable. > Multiple Surefire executions - FAILURE in an execution prevents successive > from running. > ---------------------------------------------------------------------------------------- > > Key: SUREFIRE-803 > URL: https://jira.codehaus.org/browse/SUREFIRE-803 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin > Affects Versions: 2.10 > Reporter: Ondrej Zizka > Priority: Critical > Attachments: surefire-803-failure-prevents-subsequent-executions.zip > > > Let's have multiple Surefire executions in a single module (different config > needed). > A failure of a test in one of these executions prevents running the > successive. > Surefire's testFailureIgnore is not an option because it makes a run with > failures succeed. > This behavior is undocumented. > Also, it is undesired - the module as a whole should fail, but all it's tests > should run. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira