Orchestrator - FAQ - Feature parity - Test Manager vs Orchestrator

orchestrator

latest

false

Orchestrator user guide

Getting started
- Introduction
- Orchestrator feature availability
- Licensing
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Time-to-live Periods
- Orchestrator outbound IP ranges
- Autopilot Chat in Orchestrator
- Notifications
Best practices
- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- Organizing Resources With Tags
- Exporting grids in the background
- Enforcing user-level Integration Service connection governance
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Folders
- Monitoring
- Access control
- Configuring automation capabilities
- Machines
- Solutions
- Packages
- Audit
- Credential Stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Settings
Registry
- About the Registry context
- Solution deployments
- Processes
- Resources
Cloud robots
- Cloud robots overview
- Unified Pricing licensing
- Flex licensing
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Automation Cloud™ Robots - Serverless
- Configuring VPN for cloud robots
- Configuring an ExpressRoute connection
- Live streaming and remote control
- My notifications
Automation Suite Robots
- About Automation Suite Robots
- Executing Unattended Automations With Automation Suite Robots
- Regenerating Client Secrets
- Frequently Asked Questions
Folders Context
- About the Folders Context
- Home
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
- Live streaming and remote control
  - Live streaming and remote control via RealVNC
    - Error scenarios
  - Live streaming and remote control via TightVNC
    - Error scenarios
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Process Data Retention Policy
Apps
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
Triggers
- About triggers
- Managing triggers
- Managing Non-Working Days
- Using Cron Expressions
  - Triggering jobs on the last day of the month
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
Monitoring
- About Monitoring
- Machines
- Agents
- Processes
- Queues
- Indexes
- Queues SLA
Indexes
- About indexes
- Managing indexes
Queues
- About Queues and Transactions
- Bulk uploading Queue Items using a CSV file
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
- Storing Assets in Google Secret Manager (read only)
Connections
- About Connections
- Managing Connections
Business Rules
- About Business Rules
  - Permissions for Business Rules
- Managing Business Rules
  - Creating a business rule
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
MCP Servers
- About MCP Servers
- MCP Server types
- Managing MCP Servers
- MCP Server authentication
- MCP compliance guidelines
Orchestrator testing
- FAQ - Deprecating the testing module
  - FAQ - Migrating test artifacts to Test Manager
  - FAQ - Feature parity - Test Manager vs Orchestrator
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
- Testing Data Retention Policy
Resource Catalog Service
- About Resource Catalog Service
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Troubleshooting
- About Troubleshooting
- Alerts troubleshooting
- General troubleshooting
- Frequently Encountered Orchestrator Errors

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

Deprecation guidelines​

Test Manager vs. Orchestrator - testing feature parity​

Was this page helpful?

Deprecation guidelines

Test Manager vs. Orchestrator - testing feature parity