UiPath Documentation
test-manager
latest
false
Test Manager user guide

Importing Orchestrator test sets (removed)

Reference for the removed import of Orchestrator test sets into Test Manager, which transferred test cases, schedules, results, and attachments.

Note:

This feature is removed. The Testing module in Orchestrator is no longer available, so you can no longer import Orchestrator test sets into Test Manager.

This topic describes the import process that was used to transfer test artifacts from Orchestrator to Test Manager.

For details on the removal, see the dedicated FAQ and the deprecation timeline.

What the import did​

The import transferred test sets from an Orchestrator folder you had access to into a Test Manager project. It required the TestCase.Create, TestSet.Create, and TestExecution.Create permissions, which the Project owner and Test Manager roles have.

What was transferred​

The import transferred the following details:

  • Test cases: The test case data, including name, description, and activity coverage, was preserved. New test cases were created in Test Manager for the ones that were not linked yet, and versioned test cases kept their versions. Test cases that did not belong to a test set were not migrated.
  • Test set arguments: Arguments configured for the Orchestrator test set were transferred as parameters, with their default values, to the corresponding imported test sets. Test case parameters remained unchanged.
  • Execution folder: The imported test set kept the Orchestrator folder as the execution folder.
  • Robot/User account: Any Robot or User account mapped to the Orchestrator test set was transferred to the test set in Test Manager.
  • Test set schedules: All schedules associated with the Orchestrator test set were imported in a disabled state. To use these schedules in Test Manager, you had to reactivate them.
  • Test results: The test execution results of the imported Orchestrator test sets were carried into Test Manager. Results that were not linked to an existing test set were not migrated.
    Note:
    • Duplicate test execution results generated in Test Manager after migration could affect existing integrations with Test Manager Connect, resulting in changes in dashboards and reports.
    • If you use Test Manager Connect and the migration created 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 were transferred to Test Manager.
  • Labels: Imported test sets were tagged with two labels: orchestrator-imported and imported-<date> (for example, imported-17Jun2025).
  • Created and updated by: The imported test set is listed as created and updated by an External user.

To run an imported test set via a CI/CD pipeline task, refer to Running an imported test set via CI/CD.

  • What the import did​
  • What was transferred​

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated