-
Notifications
You must be signed in to change notification settings - Fork 119
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
Test retry #522
Test retry #522
Conversation
Codecov Report
@@ Coverage Diff @@
## master #522 +/- ##
===========================================
- Coverage 80.33% 79.7% -0.63%
- Complexity 639 653 +14
===========================================
Files 74 75 +1
Lines 2029 2060 +31
Branches 259 273 +14
===========================================
+ Hits 1630 1642 +12
- Misses 251 258 +7
- Partials 148 160 +12 |
Is there information about the same tests (with the same name) in JUnitReport.xml been run on different devices and how does it handled if for some device they failed for some all passed? |
That's a good point. I'll push a fix for multi-device. |
From a quick look, this approach would probably break legitimate cases of duplicate test results in the final rollup (e.g. the use of repeatShards, unless you want to not allow the use of repeatShards with flakyTestAttempts). Deduping at the |
I pushed a new commit that names |
I think you can use repeatShards with flakyTestAttempts, however |
I have a suite with several flaky tests and that new implementation showed it well! Everything is green. |
I merged the PR. It'll continue to be in the snapshots. Thanks for testing! |
Fix #456
Read in JUnitReport.xml and remove duplicate results when
flaky-test-attempts
is > 0. For each test keep first result. If next result for the same test is successful, keep last successful result.