Planning a Test Run
1) Start out by adding a new Test Run in the Test Run Explorer.
In the Test Run form, you have the possibility to define:
Give the Test Run a name
Enter a Test Run description
Set a planned Start and End date of the Test Run
Define the Version of the Object Under Test for this Test Run
Select your Test Team
Select a Configuration set
The Test Run contains an overall Test Run Status attribute, designating the states:
Planning
Execution
Completed
2) Add Test Cases to the Test Run.
Add Test Cases to the Test Run by clicking on the Assign Tests button in the Test tab and select the Tests to add to the Test Run. The Test Grid is populated with attribute data from your Test Objects.
Test Cases can also be assigned to Test Runs from the Test Case Document Object form. Use the Action dropdown to find the Assign to Test Run action and then select the Test Run being target for the association.
3) Assigning Testers to Test Cases
Use the ellipsis button at a Test Case to assign a Tester to the Test Case.
You can batch assign Testers to a number of test cases by holding down the Ctrl-Key and selecting the cells you want to change and then select a Tester clicking on an Ellipsis button in the cell and then select a Tester in the dropdown.
Assigned Tests will show up in the Testers Your Assigned Items view.
Optionally, an email can be sent to the tester at the action of assigning. This option requires a change in the configuration.
4) Assign Test Run specific attributes
Depending on your Test Run template set up, you can also assign Test Run specific values to each Test. The available attributes and values to set are accessible from the dropdown menu in each column.
5) Assign Configurations
The Test Run concept optionally relies on the use of Configurations. When executing a Test Case, the Test Case and the related Test Result will appear in the traceability.
If you execute the Test Case again (e.g., for a new version of the Object under Test Case), the previous Test Result is now overwritten with a result of the new execution.
However, in some cases, you want to execute a particular Test Case for several variants of your Object under Test and keep each variant's result available in the traceability.
Preferably, you want to do this without having to copy the Test Case for each of your variants. Here is where Configurations come into the picture. In Aligned Elements, a Configuration is an aspect (or variant) of your Object under Test (i.e., your device) for which you want to keep results “in parallel." A Configuration is represented by a Document Object type.
Note that it is only possible to have a single Configuration Document Object type in a project.
Good examples of Configurations are; e.g.:
Device Type (Large, Middle, Small)
Application Platform (iOS, Android)
Browser type (Safari, Chrome, Firefox)
It is crucial that you carefully decide on what a Configuration signifies in your project. Changing the definition of Configuration later in the project can have severe consequences. It is essentially your traceability plan that dictates which Test Results you want to keep in parallel.
When setting up a Test Run, an important part of the planning is to decide for which Configurations you intend to run the Test Cases.
You can select a subset of the available Configurations in the Test Run main page and then use the context menu in the Test Grid to assign Configurations to the individual tests.
If you want to run a single Test with multiple Configurations in a Test Run, use the Plus-button on the Test row to assign additional configurations.
Use the ellipsis button at a Test Case to assign a Configuration to the Test Case.
You can batch assign a Configuration to a number of test cases by holding down the Ctrl-Key and selecting the cells you want to change and then select a Configuration clicking on an Ellipsis button in the cell and then select a Configuration in the dropdown.
Test Runs without Configurations
As the use of Configurations adds flexibility, they also add a degree of complexity. Therefore, Test Runs can optionally be defined to work without Configurations. This option is done on the Document Object type level and is then valid for all Test Cases of the selected type.
As there is now a one-to-one relationship between Test Case and Executed Test Case, the Executed Test Case will then receive the same ID number as the Test Case (similar to Classic Testing).
When Test Runs are configured to work without Configurations, there is no Configuration list on the Overview page and no Configuration column in the Test Grid.