-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add failOnSkippedAfterRetry option #313
Conversation
@adboyarshinov, thank you for the PR. Could you please chime in on this question from the issue? The original reporters did not follow up on it, and I am trying to understand the use case better before we commit to introducing this option. Do you have an example of such a volatile precondition that would cause tests to run, fail, and then be skipped? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All in all, looks good, well done! I left a couple of comments and suggest the following:
- Let us discuss how exactly this helps. I am still struggling to wrap up my head around the use case.
- Please add a test for this. You can use this test as an example, but I'd recommend adding one to
JUnit5FuncTest
.
plugin/src/main/java/org/gradle/testretry/internal/executer/RetryTestResultProcessor.java
Outdated
Show resolved
Hide resolved
plugin/src/main/java/org/gradle/testretry/internal/executer/RetryTestResultProcessor.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Alexander Boyarshinov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's add a test for the default behavior and we are good to go!
plugin/src/test/groovy/org/gradle/testretry/testframework/JUnit4FuncTest.groovy
Show resolved
Hide resolved
Thank you for your contribution, @adboyarshinov . We'll try to release it in 1.6.0 as soon as possible, probably this week. |
If a test is set to be skipped on it's body if certain condition meets, a retried test that is later skipped will fail the build.
Adding this option allows you to choose the behavior you want.
There is issue for this problem:
#130