[BUILD-765] Generalise re-running of flaky tests Created: 29/Apr/22 Updated: 02/Aug/22 |
|
| Status: | Open |
| Project: | Build |
| Component/s: | Poms |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Federico Grilli | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | foundation_team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Team: | |||||
| Description |
|
It may be beneficial to apply directly in parent pom what was done in DEV-1938. The default value would be 0 and single projects could change it if needed via a pom property. In many cases ITs flakiness seems related more to variables outside our control (Selenium or infrastructure quirks) than to actual issues with the underlying functionality being tested or the test-framework |