Activities Page
The Activities page offers a centralized location from which you can manage upcoming, current, and recently executed test runs for a project. The grid views on the Activities page offer filtering, sorting, and grouping options that are configurable for each user separately. You can display or hide columns, adjust the width of columns, and move columns around using click and drag.
The Activities page is split into three sections: Next Executions, Current Executions, and Last Executions. The grid views can be resized by dragging the separators between the views.
Context-sensitive menu commands are available for each test run. These commands enable you to link directly to listed execution plans, continue manual tests, manage test-run results, and more.
The Activities page makes it easier to identify match points between execution plans and to find specific execution plan information. Standard Windows keyboard shortcuts can be used to select test run entries, making it easy to select and manipulate specific sets of execution plans and test results. Sorting, grouping, and filtering functions are available through context-menu commands to help you better organize and group test runs. All of your view-customization preferences are saved along with your project and will be available to you each time you visit the Activities page.
Next Executions
The Next Executions view lists the execution plans that are scheduled to run in the future. To enhance performance when you have numerous execution plans, only the upcoming 50 execution plans are displayed. You can access additional future execution plans by using the available filtering features. To edit an execution plan, right-click the execution plan and choose Go to Execution Plan or click on the arrow to the left of the name of the execution plan. This takes you to the Executions area where you can view and edit the details of the execution plan.
By default, all execution plans are sorted by Start Time. Columns in the Next Executions view can not be sorted or grouped.
Next Executions view can be collapsed and expanded by clicking the double-arrow button on the right-hand side of the view's title bar.
For each execution plan, the Next Executions view displays the following columns:
| Column | Description |
|---|---|
| ID | Identifier of the scheduled execution plan. This column is hidden by default. |
| Execution Plan/Folder | Name of the scheduled execution plan or folder. |
| Keywords | Keywords that are assigned to the scheduled execution plan. |
| Manual Testers | For manual tests, this column contains the name of the manual tester that is assigned to the test. This column is blank when no manual testers are assigned to the test. |
| Priority | The priority that has been assigned to the execution plan. |
| Start Time | Scheduled start time of the test run. |
| Execution Plan Parent | The configuration suite, folder, or testing cycle in the context of which the execution plan is executed. Click to access the suite or folder in the Execution Plans tree. If the execution plan is not included in a configuration suite or folder, nothing is displayed. |
Current Executions
The Current Executions view lists the execution plans that are currently running (both automated and manual test runs).
To abort an execution plan that is currently in progress, click Abort in the Actions column of the execution plan. To view or edit an execution plan, right-click the execution plan and select Go to Execution Plan or click on the arrow to the left of the name of the execution plan. To view the execution's progress, right-click the automated execution plan and select View Details or click the execution plan's Run ID/Task ID link. For automated tests that run on a mobile device, the details view also allows you to view a live stream of the activities on the device. Live streams are not available for Sauce Labs devices.
As long as a manual test remains open, the corresponding execution plan remains in the list of Current Executions with a status of Pending. Click Continue Manual Test in the Actions column to open the Manual Testing window.
To view the results of a manual test, right-click the manual execution plan and select View Details, or click the execution plan's Run ID/Task ID link, to open the Results for Execution Plan page. From there, click the name of the manual test in the Assigned Tests section to open the Results dialog box. Detailed results of the manual test are displayed there. Back on the Results for Execution Plan page, click Manual Test Results to go to Manual Test view, where information about the status of the assigned manual test is available.
Page views of current executions are broken into views of 20 execution plans each. You can advance through pages using First, Last, Next, and Previous located in the lower part of the Current Executions view. Or you can type a page number into the Page field and press Enter.
For each execution plan, the Current Executions view displays the following columns:
| Column | Description |
|---|---|
| Actions | You can perform the following actions on the execution plan:
|
| ID | Identifier of the execution plan. This column is hidden by default. |
| Execution Plan | Name of the execution plan. |
| Run ID/Task ID | Manual tests receive a Run ID when they are executed. When the manual test is completed, the Run ID carries over to the Last Executions view. Automated tests receive a Task ID when they are executed. The Task ID is not carried over to the Last Executions view. Completed execution plans receive a Run ID in the Last Executions view. |
| Status | Status of the active execution plan or manual test. For automated tests, the status is indicated with a text-based value. For manual tests, the status is indicated with a colored histogram. Automated-test statuses are described textually and can be filtered. Manual tests can be filtered by checking relevant properties on the Filter submenu. |
| Keywords | Keywords that are assigned to the execution plan. |
| Executed By |
|
| Priority | For automated execution plans, when more than one execution plan is queued but only one execution server is available, the Priority determines which execution plan is executed first. The same is true if execution servers are available but multiple execution plans require an unavailable mobile device. |
| Start Time | Time when the execution plan run started. |
| Time Left | Amount of time remaining until the test is complete. For manual tests that do not have an estimated time, this column has a value of unknown. |
| Start Type | Shows how the test run was started.
|
| Starter Name | Name of the schedule, tester, or Web Service user that started the execution. |
| Start Scope | The scope defined in the Run dialog box. |
| Execution Plan Parent | The configuration suite, folder, or testing cycle in the context of which the execution plan is executed. Click to access the suite or folder in the Execution Plans tree. If the execution plan is not included in a configuration suite or folder, nothing 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. |
icon and the entry in the context menu are grayed out and such runs are ignored when you abort multiple runs.
Last Executions
The Last Executions view lists all past execution plan runs. This list can be filtered and sorted, for example by start time.
To view or edit an execution plan, right-click the execution plan run and choose Go to Execution Plan, or click on the arrow to the left of the name of the execution plan. To display the Results for Execution Plan page of an execution plan run, right-click the run and select View Details, or click the Run ID link of the execution plan. This page shows details for the selected execution plan run and includes any files and messages that were generated during the execution. To open the Results dialog box of a test, click on the Run ID of the test in the Assigned Tests portion of the Results for Execution Plan page.
To compare execution plan runs, use Ctrl+Click to select multiple runs. Right click on your selection and click Compare Automated Test Results for automated tests, or for manual tests.
Right-click on an execution plan and click Run Execution Plan to run the execution plan. Silk Central considers all tests that are currently assigned to the execution plan, not the originally assigned tests of the selected execution plan run.
To delete an execution plan run, right-click a run entry and choose Delete Results or click Delete in the Actions column of the run.
Test-result page views are broken into views of 20 test results each. You can advance through pages using First, Last, Next, and Previous at the bottom of the Last Executions view. Or you can enter a page number into the Page field and press Enter.
The Last Executions view can be collapsed/expanded by clicking the double-arrow button on the right-hand side of the view's title bar.
For each execution plan, the Last Executions view displays the following columns:
| Column | Description |
|---|---|
| Actions | You can perform the following actions on the execution plan:
|
| ID | The identifier of the executed execution plan. Unassigned tests have an ID value of N/A. This column is hidden by default. |
| Execution Plan | Name of the executed execution plan. Click the button beside the name to view the execution plan in the Execution Planning unit. |
| Run ID | ID assigned to the test run. Click the link to view details of the test run. |
| Status | Displays the number of passed, failed and not executed tests in a bar graph. Filtering, sorting, and grouping are not available for the column. |
| Keywords | Keywords that were assigned to the execution plan at execution time. |
| Executed By |
|
| Start Time | Time when the execution plan 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. |
| Product | The product under test. This column is hidden by default. |
| Version | The version that either is set by the user for this execution plan, or is read from the build information file at execution time. This column is hidden by default. |
| Build | The build that either is set by the user for this execution plan, or is read from the build information file at execution
time. If the build is tagged, it is marked bold and with
 .
|
| 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 defined in the Run dialog box. |
| Execution Plan Parent | The configuration suite, folder, or testing cycle in the context of which the execution plan is executed. Click to access the suite or folder in the Execution Plans tree. If the execution plan is not included in a configuration suite or folder, nothing is displayed. |
| 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. |