Creating Execution Plans

In the menu, click Execution Planning > Details View.

Select a folder or the project node in the Execution Plans tree.

Click

(New Child Execution Plan) on the toolbar or right-click the folder, testing cycle, or node and click New Child Execution Plan. The New Execution Plan dialog box appears.

Type a name and description for the execution plan.

Note: Silk Central supports HTML formatting and cutting and pasting of HTML content for Description fields.

Select a test container from the Test Container list.

Note: You can assign only one test container to an execution plan. Only tests from this test container can be executed.

The latest version and build that are defined within the product that the container belongs to are populated automatically in the Version and Build lists.

Select a product Version and Build from the lists. These are used when a new run of this execution plan is started. Alternatively, you can check the Read from Build Information File check box. In this case the version and build are read from the build information file on the application server at the beginning of each run. If a build information file is available on the execution server, this file is used by default for the test run, overriding the settings on the New Execution Plan dialog box.

Select a Priority for the execution plan from the list. 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.

In the Source Control Label field you can optionally specify that the execution plan is of an earlier version than the latest version. The label must refer to a version in the source control system that the test container is associated with. If this field is left blank, the latest version of the execution plan will be fetched. The Source Control Label property is only enabled if the associated test container uses a source control profile that supports versioning. Make sure to have enough free disk space on the execution server or servers when working with multiple versions of source files. Each version will be saved in its own folder on every execution server.

Tip: If you want to check out a specific branch of your repository for a specific execution plan, specify the branch name in the Source Control Label field of the respective execution plan.

Click OK to update the Execution tree with the newly created execution plan.