Skip to content
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

Repeat on failure #53

Open
occupant23 opened this issue Aug 22, 2018 · 1 comment
Open

Repeat on failure #53

occupant23 opened this issue Aug 22, 2018 · 1 comment
Assignees
Labels
codeChangeRequired During recheck issues for this popped up and needs to be addressed docsReadyForMerge Documentation was created for this issue in a separate branch which is ready to merge to develop feature Medium Priority
Milestone

Comments

@occupant23
Copy link
Contributor

occupant23 commented Aug 22, 2018

Add an annotation on test case and test function level that leads to another execution if the test case fails. If the test runs successful no further execution is required.

An optional parameter should be the number of retries (default 1).

@RepeatOnFailure(3)
@Test 
public void test()
{
    // test something 
}

Add documentation and test cases for this feature.

Possible hint for implementation with jUnit: https://stackoverflow.com/questions/8295100/how-to-re-run-failed-junit-tests-immediately.

@occupant23 occupant23 added this to the backlog milestone Aug 22, 2018
@occupant23 occupant23 added docsReadyForMerge Documentation was created for this issue in a separate branch which is ready to merge to develop Medium Priority labels Aug 22, 2018
@occupant23 occupant23 modified the milestones: backlog, v2.2.0 Sep 6, 2018
@occupant23
Copy link
Contributor Author

A temporary solution for this is to use a Surefire feature when executing the test in a CI environment.
-Dsurefire.rerunFailingTestsCount=1
Can also be set in pom.xml

@occupant23 occupant23 modified the milestones: v2.2.0, backlog Oct 12, 2018
oomelianchuk added a commit that referenced this issue Aug 19, 2022
@oomelianchuk oomelianchuk self-assigned this Aug 26, 2022
@wurzelkuchen wurzelkuchen added codeChangeRequired During recheck issues for this popped up and needs to be addressed labels Jun 26, 2024
@wurzelkuchen wurzelkuchen modified the milestones: backlog, v5.1.0 Jul 1, 2024
@wurzelkuchen wurzelkuchen modified the milestones: v5.1.0, backlog Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
codeChangeRequired During recheck issues for this popped up and needs to be addressed docsReadyForMerge Documentation was created for this issue in a separate branch which is ready to merge to develop feature Medium Priority
Projects
None yet
Development

No branches or pull requests

3 participants