[GitHub] galderz commented on issue #221: [SUREFIRE-1638] Support running tests until failure or N test runs

[GitBox <gi...@apache.org>]

galderz commented on issue #221: [SUREFIRE-1638] Support running tests until failure or N test runs
URL: https://github.com/apache/maven-surefire/pull/221#issuecomment-463960782
 
 
   @Tibor17 `skipAfterFailureCount` and `rerunFailingTestsCount` don't achieve the same thing:
   
   > Since of 2.19.1 you can use parameters skipAfterFailureCount and rerunFailingTestsCount together. This is enabled by providers surefire-junit4 and surefire-junit47. You can run again failed tests and skip the rest of the test-set if errors or failures reached skipAfterFailureCount. Notice that failed tests within re-run phase are not included in skipAfterFailureCount.
   
   `rerunFailingTestsCount` does not makes sense for my use case, I don't want to re-run failing tests. I'm waiting just for one single failure. Of course, I assume `skipAfterFailureCount` is 1 because the moment I get a failure I want things to stop. `skipAfterFailureCount` > 1 does not make sense in my problem. The moment I get a failure I have the TRACE log I need and I start debugging.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services