The Deployment page displays all of the hardware-provisioning keywords that are defined for this execution plan. These keywords are used to describe the execution environment requirements for the execution plan. An execution server only matches the selected automated execution plan if it has all keywords assigned the execution plan requires. The Deployment page also displays the users who are assigned to execute manual tests, as well as the Silk Test Classic AUT hosts that are assigned to execute Silk Test Classic tests.
Lists all manual testers who are assigned to this execution plan or folder. Click Edit to edit the list of manual testers. For additional information, see Adding or Removing Manual Testers.
| Item | Description |
|---|---|
| Assigned keywords |
Lists the keywords that are assigned to the execution plan.
|
| Keyword-related list of potential execution servers for deployment at execution time | Lists the active execution servers that have keyword lists that match the keywords list of this execution plan. All keywords in the keywords list of the execution plan must be included in the keyword list of the execution server. Click on the name of an execution server in the list to access the execution server list in . |
| Exclusive execution of assigned tests | Exclusive execution defines whether assigned tests of other execution plans having this setting disabled can be executed on the same matching execution server at the same time (Disabled), or if only tests of one single execution plan can run at the same time (Enabled). Disabling exclusive execution reduces the required execution time, and is especially useful for mobile testing, where execution plans can execute on multiple devices on a device provider at the same time. No changes to your current execution configuration are required when disabling exclusive execution. For additional information, see Exclusive Execution. |
| Distributed execution of assigned tests | Distributed execution defines whether tests of an execution plan are executed sequentially on the selected execution server (Disabled), or if they are distributed to all matching execution servers and run in parallel (Enabled). No changes to your current execution configuration are required when turning on distributed execution. For additional information, see Distributed Execution. |
| External execution of assigned tests | Switching on external execution mode for an execution plan enables you to execute test suites in an external third- party system while maintaining the corresponding automated tests and results in Silk Central. For additional information, see External Execution. |
| Video Recording |
Defines whether a video is recorded during the execution of the execution plan. This setting overrides the video recording
settings of the individual tests that are assigned to the execution plan. You can select one of the following values:
|
| Screen Capturing |
Defines whether a screenshot is captured during the execution of the execution plan. This setting overrides the screen capturing
settings of the individual tests that are assigned to the execution plan. You can select one of the following values:
|
| Execution Stop Condition |
Defines whether the execution stops if a test fails or if a test is not executed. This setting is especially useful if it
makes no sense to keep a set of tests running if even one test fails. Use this setting to save resources and to be notified
earlier if a test fails. You can select one of the following values:
Note: If an execution is stopped, the results of the successfully executed tests are preserved. Test packages (with all subordinated
tests) will always be executed to the end. They will not be stopped intermittently. However, data-driven tests will be stopped
as soon as a subordinated test fails.
|
| Silk Test Classic AUT Hostname |
Lists all Silk Test Classic AUT hosts that are defined for this execution plan. Click Edit to edit the list of Silk Test Classic AUT hosts. For additional information, see Adding a Silk Test Classic AUT Host. |
Lists the mobile device that has been selected to execute the selected execution plan. Click Edit to select a different device. Note that the device provider and your current project must be assigned to the same location, otherwise the devices will not show up in the list. For additional information, see Managing Device Providers.
Details code-analysis settings that are defined for this execution plan. Click Active/Inactive to enable or disable code analysis for this execution plan. For additional information, see Code Analysis.