Create an Execution Plan
The execution plan is the anchor of the Campaigns workspace objects that is dedicated to the execution of test cases. Test cases to be executed are added to this table. There are several ways to conceive an execution plan.
Add Test Cases to an Execution Plan Using the Library
Above the execution plan of a campaign, iteration, or tests suite, the button enables you to link test cases to the execution plan. To do so, drag and drop your selected test cases from the "Test cases repository" to the execution plan table.
Add Test Cases to an Execution Plan Using Search
To add test cases to an execution plan from the test cases or linked requirements search, click on the button in the block Execution plan. Search for test cases by using the different criteria, then click on the button to link the selected items or on the button to link all the results.
The linked requirements search enables you to search for test cases using requirements cristeria. In the results, test cases linked to the requirements matching the selected criteria are displayed.
Example: Using this search, you can add to an execution all the test cases linked to requirements with a criticality set to "Critical" and a status set to "Approved" .
Reuse a Campaign's Execution Plan in an Iteration
You can reuse a campaign's execution, with all the test cases it contains and their assignments, in the execution plan of a new iteration.
For this, in the pop-up, when you create the iteration, mark the case "Do you want to copy the campaign's execution plan?".
You cannot execute the test cases that were added to a campaign's execution plan. Its only goal is to enable you to preselect the tests to execute in the iterations. It is best for storing the list of regression tests that must be executed for every iteration.
Identify the Tests to Replay According to Previous Execution Results
Identify the Tests to Replay According to Search Results
To reexecute test cases that were already executed in a previous iteration, you can use the Campaigns workspace search to create a filter. For this, click on the button above the Campaigns workspace's library. Search ITPIs (Iteration Test Plan Item) to add to an iteration's execution plan by using the different criteria. Select the ITPIs to reuse, then click on the button above the search results.
The pop-up "Add selected items to execution plan" appears. You can:
- add the selected ITPIs to an existing iteration's execution plan to the tree;
- add the selected ITPIs to a new iteration's execution plan of the selected campaign. The new iteration will be named as follows: "Search results YYYY/MM/DD HH:MM:SS".
Thus, the Campaigns workspace search enables you to add tests to an iteration to re-execute them, especially if previously they were executed as invalid with the following execution status: "Blocked", "Failed", or "Non testable".
From the search page, you can re-execute an ITPI by clicking on the button .
Identify Tests to Replay Thanks to the Campaign Wizard
The Campaign Wizard plugin has an iteration reuse feature in the form of a wizard. It enables you to create a new iteration and its execution plan more easily using an existing iteration, based on different criteria. These criteria can be simple (most frequent cases of reuse) or more advanced (the plugin enables you to select the tests to reuse more precisely).
You must activate the Campaign Wizard plugin in the project's configuration page (Plugins anchor) to be able to use it. This plugin comes with Squash TM Premium.
The Different Steps of the Selection Process
To access the Campaign Wizard, select an iteration, click on the button , then click on the option "Campaign Wizard".
Step 1: Choose the Source Iteration
By default, the selected source iteration is the iteration from which the campaign wizard was launched. The list contains all the campaign's iterations. You can keep the source iteration's test suits and assignments in the new iteration. The field "Criteria type" enables you to choose between simple or advanced criteria to select ITPIs.
Step 2: Select Simple/Advanced Criteria
In the case where multiple criteria are selected, all the tests that answer at least one criteria are reused.
- Simple Criteria
Simple selection allows you to keep the source iteration's tests with an execution status set at "Failed" or "Blocked", the tests linked to issues, or "Regression" test cases.
- Advanced Criteria
Campaign Wizard advanced criteria can related to the tests themselves or the entities linked to the tests. To select criteria, drag and drop it/them in the block "Squash entities criteria" from the criteria selection workspace. This workspace contains the following entities:
- "Execution plan items";
- "Test cases";
- "Test suites".
It is best to use advanced criteria to identify test cases to re-execute because:
They were not validated during the previous iteration;
Their importance is set to "High" or "Very high";
They are linked to requirements with a criticality set to "Critical" or "Very critical".
Criteria in the block "Issues criteria" are different depending on the bugtracker linked to the project:
If the Squash TM project is not linked to any bugtracker: the block "Issues criteria" is not displayed;
If the Squash TM project is linked to a bugtracker other than Jira: the block "Issues criteria" is only displayed if the criteria "Keep tests linked to issues" is selected;
If the Squash TM project is linked to a Jira bugtracker (Jira.rest type): the block "Issues criteria" is displayed if the criteria "Keep tests linked to issues" is selected. If the case is marked, the criteria "Status", "Priority", and "Assigned to", and the issues reuse mode are also displayed.
Step 3: Refine the Selection of Test Cases
The test cases list appears depending on the criteria selected during the previous step. You can refine this selection by unlinking the test cases unwanted in the new iteration by clicking on the button .
Step 4: Create an Iteration
Enter a name, reference, and description for the new iteration, then click on the button [Create].
You can view the new iteration in the Campaigns Workspace with its execution plan composed of the list of test cases selected during Step 3.