[SUREFIRE-1327] Allow failed tests to run in new fork when using reuseForks and rerunFailingTestsCount

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.19.1
• Component/s: Maven Failsafe Plugin, Maven Surefire Plugin
• Environment: CentOS; Maven 3.3.3
• Assignee: Unassigned
• Reporter: Adam Lerman
• Created: 25/Jan/17 18:10
• Updated: 25/Jan/17 18:10

Description

Our project has 102 modules and 1000+ test classes. We use forkCount=1C and reuseForks=false as there are a few places in our project that use static variables and setting reuseForks to true causes tests failures. I would like to be able to reuseForks as it cuts significant time (30% or so) off the build, but hunting down the broken tests becomes a problem. I propose that when using rerunFailingTestsCount the runner should spawn a new fork for failed tests to ensure the test did not fail due to a dirty fork