0

Idea here is to run same test 10 times in CI job to make sure the test is not flaky. If one of the iteration fails then we will mark the CI job as failed and the reason for failure will be taken care.

s n murthy d
  • 13
  • 4
  • If it is a specific test case, why not go for this instead: https://stackoverflow.com/a/1493121/1531124 – GhostCat Jul 25 '22 at 10:43
  • 1
    I want to apply this approach for all newly added/modified test cases, so without changing the base test code is there any property we can pass through gradle command line to run multiple times? @GhostCat – s n murthy d Jul 25 '22 at 10:51
  • No idea here. The first problem might be: gradle is very eager to only do work ... when something has changed. So even just calling `gradle tests` again won't achieve much, you would have to at least do a clean first. – GhostCat Jul 25 '22 at 11:48

0 Answers0