Test Plan execution

This page provide information about Test Plan execution.

Test Plan workflow processing

After creating Test Plan and Test Cases under the Test Cases panel, you can start processing Test Plan execution. By default, the Test Plan has its own workflow, which is based on five statuses: Open, In progress, Acceptance and Closed. You can start running Test Plan using default workflow or change it and adapt to your project needs.

Execution

The next step of processing Test Plan is executing Test Cases. In the Test Cases panel in the Test Plan, the user can see a list of all tests that need to be performed and tests that have passed or failed. Quick filters can help to filter specific statuses of the Test Cases in Test Cases panel. For example, the user can easily find Test Cases that are waiting to be executed.

The overall status of execution is shown in the Test information panel and TP Progress custom field.

Test Plan Iterations

Test Plan Iterations is a process in which you can create and perform once again all or selected Test Cases included in given Test Plan. There are two Next iteration and Reset current iteration operations for this process, which are located in the Test information panel in Iteration section.

• Next iteration operation creates next iteration with chosen strategy.
• Reset current iteration operation reset all Test Cases and Test Case Executions to their initial state in current iteration.

Test Plan Iterations tab

The Test Plan Iterations tab shows all iterations and its Test Case execution details for given Test Plan.

1. The tab is located in Activity section on Test Plan.

   

2. The table contains a list of all iterations, historical and the latest that is currently being performed.

   The table displays columns:

   • Iteration name - shows the name/number which identify given Test Plan Iteration.
   • Iteration progress - shows the progress of Test Cases execution.
   • Executions count - shows the number of Test Cases in a given iteration.

3. The Iteration name can be changed freely. Renaming an iteration may allow you to more easily identify the tests it contains. For example, it can mean a given sprint, version, build, or other important element that will help you in reporting at a later stage.
   To rename iteration, hover over the Iteration name until the pencil appears. Click on it and enter a new Iteration name. Confirm with a tick or click outside the field. To cancel, click on the cross.

   Warning

   Users who have permission to use the Next iteration operation can change the Iteration name.

4. To see the Test Case execution details for a given iteration, click > to expand.

5. The table with details displays relevant information for Test Case execution.

   

6. To see more information, click Details. The Execution details dialog displays more detailed information for given Test Case execution.