- Getting started
- Project management
- Documents
- Change Impact Analysis
- Scheduling executions
- Executing tests
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Test Manager user guide
Importing Orchestrator test sets
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.
- 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:
- 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.
