- Getting started
- Project management
- 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
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Enabling or disabling governance in bulk for test cases
- Enforcing signing order for governed test cases
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Viewing governance information for test case logs
- Managing approvers for governed test case logs
- Managing governed test case logs in the In Work state
- Managing governed test case logs in the In Review state
- Managing governed test case logs in the Signed state
- Managing comments for governed test case logs
- Enabling governance at test case log level
- Disabling governance at test case log level
- Viewing and searching test cases
- Project operations and utilities
- Test Manager settings
- Tenant level settings
- General project settings
- Events
- Subscribing to events
- Subscribing to all events
- Unsubscribing from events
- Unsubscribing from all events
- Unsubscribing from the Notifications settings page
- Viewing notifications
- Filtering notifications
- Viewing email notifications
- Enabling email notifications for SMTP servers
- Viewing only unread notifications
- Marking all notifications as read
- Clearing all notifications
- Deleting notifications
- Customer managed keys encryption
- Audit logs
- ALM tool integration
- ALM tool integration
- Test Manager Connect
- Test Manager - Integration Service connector
- Outbound IP ranges for connectors
- Working with SAP Cloud ALM and Test Manager
- Step 1: Integrating SAP Cloud ALM with Test Manager
- Step 2: Creating automated test cases in SAP Cloud ALM
- Step 3: Creating automated test cases in Test Manager
- Step 4: Synchronizing test cases from Test Manager to SAP Cloud ALM
- Step 5: Assigning test automations to test cases
- Step 6: Executing test cases
- SAP test automation best practices
- Troubleshooting the Jira integration
- API integration
- Coding Agents for Testing
- Troubleshooting
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.
Context
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 attempts to find an equivalent automation in Orchestrator to perform the execution.
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.
For more information, see Playwright projects for test sets.
Prerequisites
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 details, see Tenant default roles.
Steps
- Go to the Test Case section of your project.
- Open a test case.
- Select the Automation tab.
- Choose Configure Automation. This action opens the Configure Automation right-hand menu.
-
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.
-
Select an automation from that location after you choose the package feed.
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 Accounttest case that was published from Studio to theAccountsfolder in Orchestrator, the Test Case Name for this automation isAccounts/Create Checking Account.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.
-
- Select Save to confirm the changes.
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.
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.
What to do next
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 details, see Configuring test sets for specific execution folders and robots.