Selecting automation

Link an Orchestrator-published automation to a test case in Test Manager using the recommended direct selection method.

To link automations with test cases, select an automation published to Orchestrator. Selecting an Orchestrator automation directly in Test Manager is the recommended method to connect an automation to a test case.

Orchestrator automations include packages published by the tm pack command of the UiPath Command Line Interface (CLI) from Playwright projects, not only packages published from Studio — refer to Playwright test automation. Test Manager falls back to automations linked from Studio if you have not selected an Orchestrator automation.

Additionally, if a test case only has a Studio automation linked but not an Orchestrator automation, then Test Manager will attempt to find an equivalent automation in Orchestrator to perform the execution.

Note:

If a Test Manager test case links to an automation from both Studio and Orchestrator, the automation selected from Orchestrator has priority over the automation linked from Studio.

Prerequisites

Note:

If you select an automation directly in Test Manager, the selected automation is not considered if the Allow execution legacy context setting is enabled (for example, when no execution folder is selected at the project or test set level). Therefore, if you want to select automations directly in Test Manager, we recommend you to disable the Allow legacy execution context tenant setting.

To select an automation from Orchestrator, make sure to perform the following:

• Publish a Studio project to the Tenant Package Feed or to another Orchestrator folder feed.
• For a Playwright package, package the project with the UiPath CLI instead — refer to Packaging Playwright projects for Test Manager. The same Orchestrator folder role and permission prerequisites apply identically to Playwright packages.
• Have one of the following roles assigned to yourself:
  • Automation User Orchestrator folder role
  • Any default role with administrative privileges
  Tip:

  Primarily, a user requires permissions to edit a test case in order to select an automation directly in Test Manager. Additional useful permissions in this context include having the Automation User role or any role with administrative privileges.

For more information on default tenant roles visit Tenant default roles.

Steps

To select an automation for a test case, follow these steps:

1. Go to the Test Case section of your project.
2. Open a test case.
3. Select the Automation tab.
4. Choose Configure Automation. This action opens the Configure Automation right-hand menu.
   1. From the Package Source dropdown list, select a feed from the corresponding Orchestrator instance. This feed should contain the Studio test case you intend to link to the Test Manager test case. The default selection is Tenant Package Feed. Only folders with their own feeds appear in the Package Source dropdown list. In a folder hierarchy scenario, only the parent folder displays in the dropdown list as all subfolders share the same feed.
      Note:

      The available package feed options are the ones for which you have administrative rights.

   2. After you choose the package feed, you can select an automation from that location.

The automation name appears under the Test Case Name column, and the published package name appears under the Package column.

Note:

The Test Case Name column displays the folder to which the automation was published to in Orchestrator, followed by the automation name. For example, if you want to select the Create Checking Account test case that was published from Studio to the Accounts folder in Orchestrator, the Test Case Name for this automation will be Accounts/Create Checking Account.

5. Select Save to confirm the changes.

Automations display a Source value of Playwright or UiPath in the picker, sorted by last-updated timestamp. For a Playwright automation, the Test Case Name column shows the full spec file path, followed by the describe-chain and test title (for example, tests/checkout.spec.ts > Checkout > cancelling the information step returns...), capped at 255 characters — refer to Playwright test case fields.

Playwright projects for test sets

When adding packages to a test set (Configure Automation > Add Packages), a Playwright package exposes a Playwright Projects dropdown listing the Playwright projects defined in that package's playwright.config.ts. Selecting one or more projects scopes the test set's execution to only the tests belonging to those projects, instead of running every test case in the set.

Because the dropdown is populated from the specific package added to the test set, the list of available projects is scoped to that package at that version:

• Adding a newer version of the same package as its own entry surfaces that version's project list, rather than merging with an older version's selection.
• Switching the version in the panel refreshes the available-projects list to that version's.
• Each execution freezes the package, version, and selected projects into a snapshot at creation time — re-executions replay that exact selection even if the test set is edited afterward.

After you select the automation from an Orchestrator package feed, you can check automation details in these fields, under Automation Assigned:

• Package TestCase Name: The folder to which the automation was published to in Orchestrator, followed by the automation name: FolderName/TestCaseName.

• Package Name: The name of the package used to publish the chosen automation. * Package Source: The Orchestrator feed where you published the package.

Updating automation

To update the automation that you selected from an Orchestrator feed, follow these steps:

1. Go to the Test Case section of your project.
2. Open a test case.
3. Select the Automation tab.
4. Choose Update Automation. This action opens the Configure Automation right-hand menu.
   1. From the Package Source dropdown list, select a feed from the corresponding Orchestrator instance. This feed is the one containing the Studio test case that you intend to link with the Test Manager test case. The default selection is Tenant Package Feed.
      Note:

      The available package feed options are the ones you have administrative rights over.

   2. After you choose the package feed, you can select an automation from that location. The automation name appears under Test Case Name, and the published package name under Package.
5. Select Save to confirm the changes.

These same steps point a test case to a newer Playwright package version. Prior execution history is preserved across the update.

Transferring test cases

If you need to transfer your test cases to a different tenant, the Orchestrator automations selected for each test case are preserved when you export and then re-import the test cases in another tenant, including automations selected from Playwright packages. For more information on exporting test cases and importing test artefacts, visit Exporting test cases and Import project.

Next steps

To execute a test set that contains test cases with automations selected from Orchestrator, you can specify the particular package and version to run the test cases. This allows Test Manager to execute test cases linked to automations from several packages within your Orchestrator feeds, using only a selected package and version.

For more information on configuring a specific execution folder and selecting a package and version, visit Configuring test sets for specific execution folders and robots.

Result

The automation is linked to the test case. The package and test case name are displayed under Automation Assigned in the Automation tab, and the test case is ready for automated execution.