Orchestrator user guide

DELIVERY:

Last updated Feb 12, 2026

FAQ - Feature parity - Test Manager vs Orchestrator

The Testing Module in Orchestrator will be fully deprecated and removed on April 30, 2026. In view of this change, refer to the deprecation guidelines and the Test Manager – Orchestrator feature parity.

Deprecation guidelines

Consult the deprecation timeline.
- Initial announcement: October, 2023
- Feature parity: April 18, 2025
- First phase of deprecation: January 1, 2026
  - Users can still create Test Sets, but should migrate to Test Manager.
- Second phase of deprecation (removal): April 30, 2026
  - Execution will no longer be allowed.
Use the migration tool to transfer your Orchestrator assets to Test Manager.

Test Manager vs. Orchestrator - testing feature parity

Table 1. Test Manager vs Orchestrator - testing feature parity
	Test Manager	Orchestrator
Purpose	A planning, analysis, and management tool for manual and automated tests. Connects automation with the agile planning and test management lifecycle.	A deployment, monitoring, and management tool for UiPath robots and test automations. Acts as a central hub to control and orchestrate automations across various environments.
Persona	Test Managers Test Users	Automation Administrators Automation Developers
Role in Test Automation	Create Requirements Define Requirements Traceability Create Test Case definitions Link test automations to definition Supports Manual Testing, manual test execution, and mixed test execution Integrates with Task Capture for test documentation needs Offers Dashboard Reports and reporting services via API Supports defect creation Supports Labels and Documents Ability to enforce execution order Ability to analyze test results Ability to override test results Ability to export data Integrates with 3rd party ALM and Test Management tools AI-powered Test Case generation AI-powered Test Insights Heatmap and UiPath Change Impact Analysis for SAP	Stores and manages Test Case automations Can assign automation to specific folder with RBAC (TM parity) Can assign automation to specific user/machine mapping (TM parity) Can select a specific Test automation version (TM parity) Create Test Schedules (TM parity) Manage test data in Test Data queues (replaced with Data Fabric) Data can be directly retrieved with workflow activities Upload test data from a .csv Data can be marked as consumed Ability to trigger a single Test Case execution (TM parity)
Shared Test Automation functions	Create Test Sets Clone Test Sets Clone Test Sets Clone Requirements Clone Test Cases Trigger automated Test Set execution Re-execute Test Cases and entire Test Sets View Test Assertions, Screenshots, and Robot Logs Analyze test results across Test Executions	Create Test Sets Clone Test Sets Trigger automated Test Set execution Re-execute Test Cases View Test Assertions, Screenshots, and Robot Logs

On this page

Deprecation guidelines
Test Manager vs. Orchestrator - testing feature parity

Was this page helpful?

PREVIOUSFAQ - Migrating test artifacts to Test Manager

NEXTTest Automation

Support and Services

Get The Help You Need

UiPath Academy

Learning RPA - Automation Courses

UiPath Forum

UiPath Community Forum

Trust and Security

Cookies Policy