Create and Organize Campaign Workspace Objects
Create Campaigns, Iterations, and Test Suites
In the Campaigns workspace, when a project is selected, you can only add a folder or campaign. You can only add an iteration when selecting a campaign, and a suite when selecting an iteration.
You can create a test suite from an iteration's execution plan via the button To activate this button, you have to select ITPIs (Iteration Test Plan Item). After the suite is created, all the selected items are automatically linked to the suite.
Deleting the folder of a campaign or iteration also deletes the ITPI of execution plans contained in that folder. It also permanently deletes the linked execution history.
Attributes of Campaigns Workspace Objects
The Information block contains basic information on Campaign Workspace objects (Campaigns, Iterations, and Test Suites):
|ID||Technical ID, needed to access the object via its URL or make API queries||X||X||X|
|The dates and the user login are automatically determined when the object is created or modified||X||X||X|
|Status||Determined by the user with a click on the field. Its possible values are:
• Planned (default valuet)
• In progress
|Progress||Automatically determined depending on the execution progress of the campaign's tests. Its possible values are:
• To be executed: no executed test in the execution plan(s)
• In progress: a number of executed tests in the execution plans
• Finished: all tests of the execution plan(s) were executed
|Editable field from which you can link only one of the project's milestones||X|
|UUID||Automatically determined when the object is created. A UUID is used to launch automated tests contained in the execution plan from a CI/CD pipeline.||X||X|
|Execution status||Editable field. Automatically determined depending on the execution status of the tests in the execution plan. The possible values are:
• In progress
• To be executed
• Non testable
|Custom Fields||Mandatory or optional. They enable you to customize objects. They can also be passed as datasets for automated executions.||X||X||X|
To learn more about how to manage automated tests execution by custom fields, please visit the page Execute an Automated Test Case
Schedule and Statistics of Campaign Workspace Objects
Scheduling a campaign or iteration enables you to enter an execution's beginning and end dates. Thus, you can set the provisional and confirmed schedule of the acceptance's execution phase. It also enables you to generate the Cumulative Progress graphs of both the iteration and the campaign.
The fields Start date scheduled on and End date scheduled on are determined by the user from the Schedule anchor of the campaign or iteration.
When the "Auto" option is marked, the Confirmed start date corresponds to the execution date of the campaign/iteration's first ITPI. This date can be changed manually.
When the "Auto" option is marked, the Confirmed end date corresponds to the execution date of campaign/iteration's last ITPI. This date can be changed manually.
In a campaign dashboard's block "Campaign cumulative progress", the button enables you to enter the provisional start and end date of its iterations.
The "Statistics" anchor of a campaign, iteration, or suite counts the number of executed tests out of the total number of tests linked to the execution plan (a/b). It also counts this ratio's progress percentage of this ratio (a/b*100 %). Finally, the anchor lists in detail the number of tests according to their execution status, in the consulted object's perimeter.
Organize the Campaigns Library
The Campaigns Workspace library is organized following a strict hierarchy: - Folders are used to organize campaigns only; - Campaigns contain iterations; - Iterations can be organized in test suites; - Test suites are the smallest object of the Campaigns workspace.
This hierarchy translates the rough size of the different Campaigns Workspace objects.
A campaign is an execution phase that goes from the first delivey of an acceptance to the production start-up. Thus, a campaign is launched before every tool start-up. Folders can be used to group the test campaigns of a tool or tool module.
An iteration is defined by the timeframe between two development deliveries during the campaign (again, an execution phase). Thus, an iteration is a sub-object of the campaign that consists of the execution plan of the tool's acceptance version. There are as many iterations as there are deliveries before the production start-up.
The test suites enable you to organize an iteration's execution plan into sections to facilitate the execution of the tests it contains. Thus, test suites enable you to organize the execution plan according to features, US, test types, and testers.
Here is the example of a possible organization of the Campaigns Workspace Library for a project:
Icons and Pill Tags
In the tree, a colored tab on the suite's name indicates its global execution status. The status given to a tests suite follows the priority order given to each of the status.
Here is the priority order of the main status. There only needs to be one test with a higher status for the rest of the suite to take this status as well:
- Blocked - Failed - Success: a test set on "success" puts the rest of the tests with an "In progress" status. Only when all the tests are marked as "Success, the suite takes the "Sucess" status.
For example, for a suite, if there is even just one test with a "Blocked" status, the suite will take the "Blocked" status no matter the status of the other tests.
Pill tags are visible the consultation page of a campaign, iteration or suite. They show: - For campaigns and iterations: the status and progress - For test suites: the execution status and progress