- Getting started
- Project management
- Documents
- Working with Change Impact Analysis
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- Linking test cases in Studio to Test Manager
- Delete test cases
- Manual test cases
- Importing manual test cases
- Document test cases with Task Capture
- Parameters
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governeed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Applying filters and views
- Importing Orchestrator test sets
- Creating test sets
- Adding test cases to a test set
- Assigning default users in test set execution
- Enabling activity coverage
- Enabling Healing Agent
- Configuring test sets for specific execution folders and robots
- Overriding parameters
- Cloning test sets
- Exporting test sets
- Applying filters and views
- Accessibility testing for Test Cloud
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Test Manager user guide
Within a test set, you can automatically execute test cases only from a default or selected Orchestrator folder (also known as the Execution folder). You can specify an execution folder either at project level or at test-set level. If you specify an execution folder at both levels, the test-set level folder overrides the project-level folder. If you specify an execution folder only at project level, the test-set level folder inherits the project-level folder.
If you want to execute the test cases from a specific package and version within a folder, you can select the package and its corresponding version. Moreover, you can also set a specific user or robot account that can execute the test set.
Tenants which have the Allow legacy execution context setting enabled can still perform automated test execution without specifying an execution folder. However, this type of execution will be deprecated soon. To continue working, you must specify an execution folder either at project level or at test-set level, as described in the current topic. We recommend executing your tests using specific execution folders.
Prerequisites
You can configure the execution of a test set for a specific Orchestrator folder, and robot account, only if the Allow legacy execution context tenant setting is toggled off. For more information about the setting, visit Tenant level settings.
Selecting an execution folder and account
To specify an execution folder at project level, follow the steps in the Automation project configuration – Assigning a default folder topic.
To specify an execution folder at test-set level, follow these steps:
- Go to Test Sets and select the test set for configuration.
- In the Test Cases tab, select Configure Automation.
- From the Execution folder dropdown list, select a folder of your choice.
Note:
This choice will populate the Select Robot dropdown list with robot accounts available in the selected folder.
If you do not want to select a specific folder, opt for None, which will use the Default folder of the tenant, if it exists. 4. From the Select Robot dropdown list, choose a robot account. The default value is Any User/Robot account, which allows you to execute the test set using any robot available in the selected folder. 5. Select Save to confirm the selection.
Selecting a specific package and version
In addition to the execution folder and robot account, you can also select a specific package and version from which to run test cases. To select a specific package and version, perform the following steps:
- Navigate to Test Sets and open a test set.
- Go to the Test Cases tab.
- Select Configure Automation.
- To define a package and version, the following options are available:
- Autoselect Packages: Automatically selects all packages located in the execution folder and their latest versions, based on the test cases assigned to the test set.
- Add automation: Allows you to manually select the desired packages and corresponding versions. Use the following steps:
- From the Package dropdown list, select a package.
- From the Version dropdown list, select a version for that package.
- Use Select to finalize the selection.Repeat the previous steps for each package you wish to add to the test set.
Figure 1. Display of Selected Automations menu illustrating the chosen execution folder and robot account, associated packages, and their respective versions for a specific test set

Selecting a specific host machine
Select a host machine to enforce execution for all the test cases in a test set. If the host machine is not available, the execution waits, and then times out.
This feature is available in Test Manager only when delivered through Test Cloud.
- Navigate to Test Sets and open a test set. Select Save to confirm the selection
- Go to the Test Cases tab.
- Select Configure Automation.
- Select an Orchestrator execution folder.
- Under Runtime type, select one of the options, depending on your license type: Testing, App Testing, Cloud – Serverless Testing, Cloud – Serverless, Cloud – VM Testing, Cloud – VM.
- Under Robot account, select a robot account. The default value is Any User/Robot account, which allows you to execute the test set using any robot available in the selected folder.
- Under Machine template, select Any Machine or a specific machine template. The Host Machine field becomes available.
- Under Host Machine, select Any Connected Machine or a specific host machine.
- (Optional) Select or define a package and a version.
- Select Save to confirm the selection.