test-manager
latest
false
- Getting started
- About Test Manager
- About Autopilot
- Getting started
- Conditions
- Flex: Licensing Test Manager
- Quickstart guide
- Project management
- Documents
- Heatmap
- Prerequisites
- Step 1: Installing the UiPath SAP Add-On in your SAP system
- Step 2: Configuring your SAP system
- Step 4: Configuring UiPath Test Manager
- Web service connection
- Web service - OAuth connection
- RFC connection
- CSV file connection
- Working with Heatmap
- Working with Change Impact Analysis
- Requirements
- Creating requirements
- Cloning requirements
- Exporting requirements
- Quality-check requirements
- Generate tests for requirements
- Finding obsolete tests based on requirements
- Applying filters and views
- Test cases
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- Automate test cases
- Selecting automation
- Unlinking automation
- Linking test cases in Studio to Test Manager
- Delete test cases
- Manual test cases
- Importing manual test cases
- Parameters
- Applying filters and views
- Test sets
- Importing Orchestrator test sets
- Creating test sets
- Adding test cases to a test set
- Assigning default users in test set execution
- Enabling activity coverage
- Configuring test sets for specific execution folders and robots
- Overriding parameters
- Cloning test sets
- Exporting test sets
- Linking Orchestrator test sets
- Applying filters and views
- Executing tests
- Executing manual tests
- Executing automated tests
- Executing test cases without a test set
- Executing mixed tests
- Creating pending executions
- Enforcing an execution order
- Re-executing test executions
- Scheduling executions
- Troubleshooting automated executions
- FAQ - Feature parity - Test Manager vs Orchestrator
- Accessibility testing for Test Cloud
- Test results
- Analyze test results
- Deleting test case results
- Defect synchronization
- Generate test insights report
- Autopilot best practices
- Quality-check requirements
- Generate tests for requirements
- Convert text into code
- Automate manual tests
- Generate synthetic test data
- Generate test report
- Project operations and utilities
- Import project
- Export project
- Export data
- Bulk operations
- Reports
- Test Manager dashboard reports
- Using external reporting tools
- Migrating Test Manager artifacts to other delivery options
- Testing Data retention policy
- Test Manager settings
- Tenant level settings
- User and group access management
- Custom fields
- Prompt library
- General project settings
- Automation project configuration
- My notifications
- ALM tool integration
- ALM tool integration
- Test Manager Connect
- Out-of-the-box connectors
- SAP Cloud ALM
- SAP Solution Manager integration
- Setup and configuration
- Configuring user machine
- Configuring SAP Solution Manager
- Configuring system under test
- SAP Solution Manager command line
- Use case scenarios
- Atlassian Jira
- Xray for Jira
- Azure DevOps
- Webhooks
- Redmine Integration
- API integration
- Test Manager API integration
- Integrating your tool with Test Manager
- API Scopes
- Test Manager API
- Test Manager API
- API version
- Test Manager URL
- API references
- Troubleshooting
- Troubleshooting Test Manager
Test Manager user guide
Last updated Mar 24, 2026
Before the deprecation of the Orchestrator Testing tab, you need to transfer all remaining test artefacts to Test Manager. You can import your Orchestrator test sets from the Test Sets section of your project.
For information on the deprecation of the Orchestrator Testing tab, visit the dedicated FAQ, and the deprecation timeline.
Note: You cannot import the same Orchestrator test set twice within
the same project.
- Ensure you have access to all the Orchestrator folders containing the test sets you want to import.
- To initiate the import process,
you need at least the following permissions in Test Manager:
TestCase.CreateTestSet.CreateTestExecution.Create
Note: Project owner and Test Manager are the user roles in Test Manager which have the all of the above permissions assigned.
- Go to the Test Sets section of your project.
- Select Import.
The Import Orchestrator Test Sets window opens.
- From the Select Folder dropdown list, choose the Orchestrator folder from where you want to import the test sets.
- Select the test sets that you want to import into Test Manager.
- Select Import to trigger
the import process.
After the import process finishes, a notification confirms that the test set was imported successfully. If the Orchestrator test set includes executed results, you will also see a Test executions imported successfully notification. Depending on your notification preferences, these notifications may appear both in-app, via email, or both.
Once the test set is imported, note the following:
- Imported test sets from Orchestrator are tagged with two labels to help
with test organization:
orchestrator-importedimported-<date>(for example:imported-17Jun2025)
- The imported test set is listed as created and updated by an
Externaluser.
- Imported test sets from Orchestrator are tagged with two labels to help
with test organization:
You cannot run a test set which was imported into Test Manager via a CI/CD pipeline task. To work around this, follow these steps:
- Go to the Testing tab in Orchestrator.
- Clone the imported test set that you want to execute.
- Use the clone for executing the test set through a CI/CD pipeline task instead of the original imported test set.
Note: Cloning a test set does not copy its execution history. To
preserve recent execution data within Test Manager, we recommend that you import the
cloned test sets into Test Manager after running it via CI/CD.
After importing the Orchestrator test sets into Test Manager, the following details
will be transferred:
- Test cases: The test
case data, including name, description, and activity coverage, are preserved
from Orchestrator to Test Manager. New test cases are created in Test
Manager for the ones that are not linked yet, and versioned test cases
maintain their versions.
Note: Any test case that does not belong to a test set will not be migrated. If you want to migrate such a test case, then assign it to a test set, and then migrate the corresponding test set.
- Test set arguments: Arguments configured for the Orchestrator test set transfer as parameters, with their default values, to the corresponding imported test sets. Test case parameters remain unchanged.
- Execution folder: The imported test set maintains the Orchestrator folder as the execution folder.
- Robot/User account: Any Robot or User account mapped to the Orchestrator test set is transferred to the test set in Test Manager.
- Test set schedules: All schedules associated with the Orchestrator test set are imported in a disabled state. To use these schedules in Test Manager, you must reactivate them.
- Test results: The test
execution results of the imported Orchestrator test sets are carried into
Test Manager.
Note:
- Test execution results that are not linked to an existing test set will not be migrated. You will still be able to view them in Orchestrator's Testing tab.
- If duplicate test execution results are generated in Test Manager after migration they can impact existing integrations with Test Manager Connect, resulting in changes in dashboard and reports.
- If you use Test Manager Connect and the migration creates a large number of artifacts, you may notice increased synchronization activity with external ALM tools integrated with Test Manager.
- Attachments: Any attachments tied to test cases within the imported Orchestrator test sets are transferred to Test Manager.
- Migrating test sets linked from Orchestrator: After you migrate test sets previously linked from Orchestrator to Test Manager you need to manually remove them from Test Manager.