In batch runs, you can set the "Retry Failed Tests" option to re-run any test cases that failed automatically.
Test failures caused by environmental factors — such as temporary network disruptions or server issues — can be difficult to prevent entirely. We recommend utilizing this feature to handle such situations.
Note that setting a high retry count is unlikely to significantly improve success rates and may also cause persistent defects to go undetected. For this reason, we recommend setting the retry count to 1 or 2.
How to Configure
Navigate to the project screen and click "Details" from the "Batch runs" tab.
Specify the number of retries under "Retry for failed tests" in the "Advanced settings" tab.
How to check the logs
You can check whether a retry was performed in the test run log of an individual test result.
Q&A
Q. Is the retry performed per test case or for the entire batch run?
Retries are performed on a per-test-case basis.
For example, in a batch run consisting of test cases 1, 2, and 3, if test case 2 fails midway through, the retry will start from the beginning of test case 2.
Q. Can I check whether a retry was performed from the test results list screen?
Currently, this cannot be checked from the test results list screen. Instead, you will need to check the "Test run log" tab within an individual test result.
We have received requests to improve this and have filed them as feature requests below.
If you would like this feature to be implemented, please vote for it below. (See here for how to vote.)
- Enable identification of successful test results in the list after retrying
- Make logs for failed test retries easier to understand
Q. Is there a feature to retry only under certain conditions, or to specify the number of retries per test case?
Currently, these features are not available.
If you would like this feature to be implemented, please vote for it below. (See here for how to vote.)
- Apply retry on failure only under specific conditions such as when the application fails to launch immediately after test case starts
- Customize retry counts for failed batch runs