# Configuring test sets for specific execution folders and robots

> 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.

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.
:::important
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](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/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](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/automation-project-configuration#assigning-a-default-folder) topic.

To specify an execution folder at test-set level, follow these steps:

1. Go to **Test Sets** and select the test set for configuration.
2. In the **Test Cases** tab, select **Configure Automation**.
3. 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:

1. Navigate to **Test Sets** and open a test set.
2. Go to the **Test Cases** tab.
3. Select **Configure Automation**.
4. 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:
     1. From the **Package** dropdown list, select a package.
     2. From the **Version** dropdown list, select a version for that package.
     3. 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

   ![Display of Selected Automations menu illustrating the chosen execution folder and robot account, associated packages, and their respective versions for a specific test set](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-display-of-selected-automations-menu-illustrating-the-chosen-execution-folder-and-robot-account-associated-packages-and-their-respe-323c7d52-f1850844.webp)

## 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.
:::note
This feature is available in Test Manager only when delivered through Test Cloud.
:::

1. Navigate to **Test Sets** and open a test set. Select **Save** to confirm the selection
2. Go to the **Test Cases** tab.
3. Select **Configure Automation**.
4. Select an Orchestrator execution folder.
5. 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**.
6. 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.
7. Under **Machine template**, select **Any Machine** or a specific machine template. The **Host Machine** field becomes available.
8. Under **Host Machine**, select **Any Connected Machine** or a specific host machine.
9. (Optional) Select or define a package and a version.
10. Select **Save** to confirm the selection.