| 9.3. Test Runs | ||
|---|---|---|
|
Chapter 9. Evaluate |  |
| 9.3. Test Runs | ||
|---|---|---|
|
|
Chapter 9. Evaluate | |
This page lists all test runs that have been executed in the selected project.
![[Note]](images/note.png) |
Note |
|---|---|
|
Only fully executed test cases are displayed on this page. Suspended test runs can be continued at Section 8.4, “Continue Test Run”. |
The table shows the following values:
|
ID |
The automatically assigned ID. |
|
Additional Information |
A tooltip appears when the cursor is placed over the icon shown here. |
|
Start |
The start time of the test run. |
|
Assignee |
The name of the user to whom the test run is assigned. |
|
Iteration |
The iteration in which the test run was executed. |
|
Job |
The task with which the test run was executed. |
|
Test Case/Suite |
The ID of the test case or test suite of the test run. |
|
Test Environment |
The test environment in which the test was executed. |
|
System Under Test |
The system under test that was tested. |
|
Results |
The number of test case results. |
|
Passed |
The number of test case results with the status/verdict "Passed". |
|
Failed |
The number of test case results with the status/verdict "Failed". |
|
Error |
The number of test case results with the status/verdict "Error". |
|
Inconclusive |
The number of test case results with the status/verdict "Inconclusive". |
|
Skipped |
The number of test case results with the status/verdict "Skipped". |
|
Action |
The executable actions. |
The following actions can be performed in the action column:
If a test run has been deleted, it is initially marked with a deletion marker and is only visible to administrators. For deleted test runs, the following actions are available instead of Delete:
|
Deleting a Test Run |
|---|---|
|
When a test run is deleted, the associated test case results and test suite results are also deleted Once all test runs for a specific system under test or test environment have been deleted, the respective system under test or test environment may also be deleted. Otherwise, they remain locked for deletion. |
Certain actions can also be applied to several test runs at once. To do this, select the test runs to which the action is to be applied in the leftmost column.
The following bulk actions are supported for test runs:
For additional information, see Section 5.2.3.1.5, “Bulk Actions”.
The following operations can be performed in the line above the table on the right:
All operations are described in detail in Section 5.2.3.1, “Overview Page”.
The “Test Run Report” shows the details of a test run including its execution date, executor, system under test, test environment and the number of Passed, Failure, Error, Inconclusive and Skipped results. It can be generated in PDF or HTML format. An example PDF is shown in Figure 9.17.
Each test run has its own detail page. By clicking on the ID of the respective test run or on the in the action column, you can access the detail page. All test case results and, if available, the test suite result of the test run are displayed in tables here.
The following tabs are available: Properties, User Defined and Results. At first invocation this is the Results tab with the sub tabs Test Case Results and Test Suite Results.
The action toolbar is located in the top right corner of the title bar The following actions can be performed on the detail pages:
|
Open execute view |
Re-execute this test run. |
|
Open print view |
A print-ready view of the iteration can be created here. With a click on the icon this opens in a new browser tab. Print views are described in detail in Section 5.2.3.2.1, “Print Pages”. |
|
Create Bookmarks |
Each individual detail page can also be reached directly via a hyperlink. By clicking on the icon this link is copied to the clipboard. The creation of bookmarks is described in detail in Section 5.2.3.2.2, “Bookmarks”. |
|
Browse |
Use the green arrows at the very top right to switch between the properties present on the previous page. |
The Properties tab shows the following information:
|
ID |
The automatically assigned ID. |
|
Executor |
The user who executed this test run. |
|
System under Test |
A drop-down menu for selecting the assigned system under test. |
|
Test Environment |
A drop-down menu for selecting the assigned test environment. |
|
Iteration |
The iteration in which the test run was executed. |
|
Assignee |
The user to whom this test run is assigned. |
* A test manager or administrator can retroactively correct the entries here. This may be necessary, for example, in the case of an incorrect entry when starting the test run.
You can create your own fields to meet individual requirements. For further information please refer to Section 5.2.3.2.4, “User Defined Properties”.
The Results tab splits into the Test Case Results subviews. and Test Suite Results. The table displays the following values:
|
ID |
The automatically assigned ID. |
|
Additional Information |
A tooltip appears when the cursor is placed over the icon shown here. |
|
Start |
The start time of the test run. |
|
Iteration |
The iteration in which the test run was executed. |
|
Test Case |
The test case. |
|
Test Environment |
The test environment in which the test was executed. |
|
System Under Test |
The system under test that was tested. |
|
Executor |
The name of the user who last executed the test run. |
|
Duration |
The execution time. |
|
Result |
The test case result (Passed, Failed, Error, Inconclusive, Skipped). |
|
Action |
The executable actions. |
The tab Changes shows the change history of this test run.
For a detailed description of the Changes view, see Section 5.2.3.2.8, “Change History”.
|
|
 |
|
| 9.2. Reports |  |
9.4. Test Case Results |
