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

Feature Request: fail fast invocationCount and successPercentage logic #588

Open
yapith opened this issue Jan 11, 2015 · 2 comments
Open

Comments

@yapith
Copy link

yapith commented Jan 11, 2015

There should be an option to not run a test with configured invocationCount and successPercentage when the successPercentage is already met.

For example: if (invocationCount == 2 && successPercentage is 50) then the test should only retry if the first attempt fails.

It answers the question of whether a test meets the desired success rate without consuming additional computing resources.

P.S. This requirement is moot if the invocations are run in parallel. In my case, the integration tests are memory bound that single threaded retry is desired.

@yapith
Copy link
Author

yapith commented Jan 11, 2015

In the mean time, what is the best work around to achieve the stated problem? I'm currently considering a custom TestRunner implementation.
I appreciate the advice.

@perlun
Copy link

perlun commented Feb 1, 2019

I'm also looking for something similar, but for different reasons: I am chasing a difficult bug where I want to re-run a test 10, 100 or even 1000 times. It's enough to know that it failed one time, I don't need to run the remaining 5, 50 or 500 times (or worse). @yapith did you find a workaround?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants