Rerun failed tests in Low Code Automation

Rerun failed tests automatically or manually in Low Code Automation.

Builds may encounter failures due to website updates, third-party dependencies, environment changes, or test data issues. Low Code Automation allows you to rerun only the tests that failed in a build, eliminating the need to rerun the entire test suite. This flexible approach helps you quickly identify and resolve issues while optimizing testing time and resources.

You can rerun failed tests in the following ways:

• Automatic rerun: Configure the test suite to automatically rerun failed tests once as soon as a build fails.
• Manual rerun: Trigger a rerun manually from the Builds page after the build fails.

Automatic rerun of failed tests

You can configure your test suite to automatically rerun failed tests when triggered via scheduler. During test suite creation, after scheduling the tests, enable the Rerun failed tests once option.

Once the build finishes, any failed tests are automatically rerun and the build gets updated with the latest results for the failed test runs.

Manual rerun of failed tests

You can also manually rerun failed tests. Go to Builds and select the desired build which you want to rerun. Click the Rerun icon at the top.

Build information post rerun

After the rerun is finished, a Rerun icon appears next to each failed test. Hover over to view detailed information.

You can see the following information:

• Once the rerun of the failed tests is finished, the status of the tests is updated within the same build.
• The overall status of the build is also updated based on the execution results.
• The total build duration after reruns is the sum of the main run and all rerun durations.
• You can also view the result of a previous run by hovering over any test execution result that was rerun within the build.
• Previous rerun history can also be viewed in the build’s metadata.