Test Reruns

A Test Rerun is a repeat execution of a previous Test Run using the same configuration.

Reruns are used to validate results without redefining the test or changing execution settings. Each rerun is recorded as a separate execution and does not replace the original Test Run.

Test Reruns are typically used after an issue has been addressed or when execution needs to be validated again.

Common scenarios include:

Reruns ensure that results can be compared directly across executions.

A rerun repeats a previous Test Run using the same test definition, devices, and configuration.

Creating a new Test Run allows changes to be made to the test setup, such as selecting different devices or modifying execution parameters.

Both approaches create independent execution records, but reruns preserve the original execution context.

Reruns are managed through Test Management and appear as separate Test Runs.

Each rerun is listed with its own name and execution details. The rerun name includes a reference to the original Test Run ID, which can be used to identify the source of the rerun.

Reruns can be reviewed individually to evaluate execution results after remediation or validation.