- Getting started
- Project management
- Working with Change Impact Analysis
- Create test cases
- Cloning test cases
- Exporting test cases
- Linking test cases in Studio to Test Manager
- Delete test cases
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Enabling or disabling governance in bulk for test cases
- Enforcing signing order for governed test cases
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Viewing governance information for test case logs
- Managing approvers for governed test case logs
- Managing governed test case logs in the In Work state
- Managing governed test case logs in the In Review state
- Managing governed test case logs in the Signed state
- Managing comments for governed test case logs
- Enabling governance at test case log level
- Disabling governance at test case log level
- Viewing and searching test cases
- Executing test cases without a test set
- Executing mixed tests
- Creating pending executions
- Re-executing test executions
- Troubleshooting automated executions
- FAQ - Feature parity - Test Manager vs Orchestrator (removed)
- Project operations and utilities
- Test Manager settings
- Tenant level settings
- General project settings
- Events
- Subscribing to events
- Subscribing to all events
- Unsubscribing from events
- Unsubscribing from all events
- Unsubscribing from the Notifications settings page
- Viewing notifications
- Filtering notifications
- Viewing email notifications
- Enabling email notifications for SMTP servers
- Viewing only unread notifications
- Marking all notifications as read
- Clearing all notifications
- Deleting notifications
- Customer managed keys encryption
- Audit logs
- ALM tool integration
- ALM tool integration
- Test Manager Connect
- Test Manager - Integration Service connector
- Outbound IP ranges for connectors
- Working with SAP Cloud ALM and Test Manager
- Step 1: Integrating SAP Cloud ALM with Test Manager
- Step 2: Creating automated test cases in SAP Cloud ALM
- Step 3: Creating automated test cases in Test Manager
- Step 4: Synchronizing test cases from Test Manager to SAP Cloud ALM
- Step 5: Assigning test automations to test cases
- Step 6: Executing test cases
- SAP test automation best practices
- Troubleshooting the Jira integration
- API integration
- Coding Agents for Testing
- Troubleshooting
FAQ - Feature parity - Test Manager vs Orchestrator (removed)
Feature parity comparison between Test Manager and the Orchestrator Testing module, which is removed.
The Testing module in Orchestrator is removed. In view of this change, refer to the removal guidelines and the Test Manager – Orchestrator feature parity.
Removal guidelines
- The deprecation timeline includes the following milestones:
- Initial announcement: October 2023
- Feature parity: April 18, 2025
- Migration tool available: June 25, 2025
- First phase of removal: January 1, 2026
- Orchestrator no longer displays test results, and you cannot execute tests or test sets from Orchestrator.
- Second phase of removal: July 31, 2026
- Test set creation and execution in Orchestrator is removed. The Add Test Set button and the Test Schedules tab are removed from the UI.
- API-based test execution is disabled. Requests receive a 403 response, except for tokens carrying the S2S internal claim, which remain functional for Test Manager.
- Test sets remain visible and read-only, so you can still view them, but you can no longer migrate them to Test Manager.
- Test data queues and the test data queue activities are also removed as of July 31, 2026. Use Data Fabric / Data Service instead.
- The migration tool was available from June 25, 2025 to transfer Orchestrator assets to Test Manager. It can no longer be used to migrate remaining artifacts.
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 |
|
|
| Role in Test Automation |
|
|
| Shared Test Automation functions |
Masked or anonymized production data can be used as test data by uploading it to Data Service (Data Fabric) as an Excel file and linking it to a Studio automation. Direct test data linking from Test Manager test sets is planned as a future enhancement.
Process status and test case status for assertion failures
A plain Orchestrator job's status only reflects whether the job itself failed to run, such as an unhandled exception — it does not reflect the pass/fail result of individual Verify or assertion activities inside the workflow. A process with one or more failing Verify activities can still show as Passed at the job level unless an exception is thrown, or unless the Verify activity's Continue on error property is set to false.
A Test Manager test case execution does not have this gap: its status reflects the worst of the job status and the assertion results, so a failing Verify activity always produces a failed test case, regardless of the underlying job status.
Test set retention
In Orchestrator, Test Sets could use a "Transient" SourceType that auto-deleted the test set after a period of time. Test Manager has no equivalent auto-delete mechanism — all test set deletion must be performed manually.