# Selecting a specific host machine

> Select a specific host machine to enforce execution for all test cases in a test set when using Test Cloud.

Run the executions of a test set on one host machine in Test Cloud. If the selected 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.
:::

## Steps

1. Navigate to **Test Sets** and open a test set.
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 executes 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.

<!--
Running tests under a tester's own credentials

If a functional or service account does not have access to the application under test, and testers must authenticate with their own SSO and MFA credentials, point the test set to the tester's own machine instead of a shared robot. This requires an App Test Robot unattended runtime license and an App Test Developer license, with UiPath Assistant and Studio configured on the tester's local machine.

1. Install UiPath Assistant and Studio on the tester's local machine.
2. Connect the machine as a robot in the selected Orchestrator execution folder.
3. Follow the steps described earlier in this topic, under "Selecting a specific host machine," to configure the test set to use that machine and the tester's robot account.

When the test set runs, execution uses the robot connected through the tester's own UiPath Assistant, under the tester's own logged-in session, so the automation authenticates the same way the tester would, including SSO and MFA prompts. This still counts as unattended execution from Test Manager's perspective, but effectively provides attended-style access to applications that require a personal, MFA-protected account rather than a shared functional account.

Before publishing: confirm the exact license name ("App Test Robot unattended runtime license") against the current commercial licensing catalog, then remove this comment to make the section visible.
-->

## Result

The test set is configured to run all its test cases on the specified host machine, using the selected execution folder, runtime type, robot account, and machine template.