The Runs page shows statistics regarding all the runs of the selected execution plan.
For configuration suites, the page displays all runs of the included configurations.
For testing cycles, the page displays all runs of the included execution plans and folders.
The page is split into two separate sections, one listing the execution plan runs, and the second listing the test runs for the execution plan run selected in the first section.
The grids are customizable: You can display or hide columns, adjust the width, and drag the columns around to change their order. Click on the columns to sort, group or filter the content in the grids.
To open the Execution Plan Run Results dialog box, right-click on a run and choose View Details. To compare multiple execution plan runs, use Ctrl+Click or Shift+Click to select the runs. Right-click on your selection and select Compare Automated Test Results.
The execution plan runs section lists the runs of the selected execution plan. Use the menu bar on the bottom of this section to define how many rows to display per page and to navigate through the pages. The page shows the following columns for each run:
Column | Description |
---|---|
Actions | Actions that you can perform on the execution plan.
|
ID | The identifier of the execution plan. |
Execution Plan | The name of the execution plan that was executed. This column is only displayed for configuration suites. |
Status | Status summary of the run. A bar lists the amount of passed, failed, and not executed tests. The run status of each assigned test is shown in the second section of the page. |
Run ID | Identifier of the execution plan run. Click to access the results of the run. |
Keywords | Keywords assigned to the execution plan. |
Executed By | Name of the execution server on which the run was executed. For manual tests the name of the person who executed the run is listed. |
Product | The application under test. |
Version | The version is either set by the user for this execution plan, or is read from the build information file at execution time. This information can be set in | .
Build | The build is either set by the user for this execution plan, or is read from the build information file at execution time. This information can be set in | . If the build is tagged, it is marked bold and with .
Start Time | Time the run started. |
Duration | Time consumed to execute all included tests. Includes the duration of the setup and cleanup test and the time consumed to fetch automation files and code coverage, launch execution tools, and other tasks. For manual executions this is the time between starting and finishing the execution. |
Start Type | Shows how the test run was started. Manually, through a Web Service, or from a schedule. |
Starter Name | Name of the schedule, tester, or Web Service user that started the execution. |
Start Scope | The scope specified in the Run dialog box. |
Execution Plan Parent | The name of the execution plan parent. |
Run Comment | You can use this column to add information to the run. To edit the comment, right-click on the run and select Edit Run Comment. |
Mobile Device Selection | The device filter that was specified on the Deployment page, if the execution plan is configured to run on a mobile device. |
Used Device | The device that matched the device filter and was actually used to execute the tests, if the execution plan is configured to run on a mobile device. For manual tests, the device that was last selected by a tester in this execution plan is displayed. |
If you have assigned attributes to your execution plans, you can select to display them in the grid. Attributes are freely definable characteristics that can be applied to execution plans. You can use attributes for filtering and reporting purposes. |
The Test Runs section lists the test runs for the selected execution plan run. Use the menu bar on the bottom of this section to define how many rows to display per page and to navigate through the pages. The page shows the following columns for each run:
Column | Description |
---|---|
Actions | Actions that you can perform on the test run.
|
Status | Status summary of the run. For a single test a single status is shown. A bar lists the amount of passed, failed, and not executed tests for a test package or suite node. |
Status Reason | The reason why a specific test run has the status Passed, Failed or Not Executed. |
Run ID | Identifier of the test run. Click to open the Test Run Results dialog box. |
ID | Identifier of the test. This column is hidden by default. |
Test | Name of the test. Click to access the test in | . The icon corresponds to the test type.
Version | The version the run was executed against. |
Start Time | Date and time the run started. |
Duration | Duration of the test run. |
Executed By | Name of the execution server on which the run was executed. For manual tests the name of the person who executed the run is listed. |
Issues Found | Displays the amount of issues that are assigned to the test run. When no issues are assigned to the test run, the column is empty. Click on the link to access the issue in the Issues page of . |
Errors | Number of errors that occurred in the run. |
Warnings | Number of warnings that occurred in the run. |
Build | The build the run was executed against. |
Run Comment | For Silk Performer test runs, Silk Performer uses this column to add information to the test run when uploading results. For all other test types, you can use this column to add information to the run. To edit the comment, right-click on the run and select Edit Run Comment. |