Test Plan Runs

Re-execute test cases and compare their results

Vishal Vaswani avatar
Written by Vishal Vaswani
Updated over a week ago

There is often a need to get some or all of the test cases re-verified before a test plan can be called as completed, or there are test plans that are used as long as a project is active. In both the cases to re-execute a set of test cases based on their current execution status (and configuration, if any) in a test plan a RUN can be created.

When a new test plan is added a first RUN is automatically created by default, and a run is active until all the test cases in the test plan get executed. With the execution of test cases the progress of a RUN can be tracked by switching to the Runs tab of a test plan, along with the total time spent on the RUN so far.

Create a new run

Once all the test cases under a Test Plan have been executed then if needed it is possible to add a new run.

  1. Click on Create a new run button

  2. If you are using configurations, then select for which configuration, a new run should be created, you can also select all configurations

  3. Select one or more status (results) to get the test cases selected for re-execution.

  4. Select one or more users from the dropdown if the assignee need to be changed for this new RUN or select original assignees option if you want to assign these test cases to testers who ran the previous RUN.

When a new RUN is added all test cases that satisfy the criteria are set to have unexecuted status, and assignee for these test cases would again be based on selection made by the user who added the RUN.

Run wise status

When there are more than one RUNs added to a test plan then on Runs tab a Run wise status graph is added to show a comparison between current and previous RUNs test cases in a test plan had been through.

It is a bar graph and each bar represents a RUN. Please note that the total number of test cases in test plan would always be depicted in each bar irrespective of the number of test cases selected for re-execution at the time of adding that RUN.

Did this answer your question?