- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Enforced encryption
- Settings
- Deployments registry
- Notifications
- Folders Context
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Indexes
- Queues
- Assets
- Connections
- Business Rules
- Storage Buckets
- Agent Gateway
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
FAQ - Deprecating the testing module (removed)
Answers to common questions about the removal of the Orchestrator Testing module and its implications.
This Frequently Asked Questions (FAQ) page provides answers regarding the removal of the Testing module in Orchestrator and its implications.
Visit the Deprecation timeline to check the chronological details of this change.
What does "feature parity" mean?
Feature parity refers to mirroring the capabilities of the Testing module in Orchestrator in Test Manager, making the transition straightforward, while minimizing the loss of functionality. Test Manager reached feature parity with the Orchestrator Testing module on April 18, 2025. No additional features were added to the Testing tab.
What changes are needed?
The Testing module in Orchestrator is removed. As of January 1, 2026, the Testing module no longer displays any test results, and you cannot execute tests or test sets from Orchestrator. As of July 31, 2026, test set creation and execution in Orchestrator is removed, and test sets remain visible and read-only. Use Test Manager instead.
Remaining test artifacts can no longer be migrated 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.
How should future testing work be strategized? What are the next steps?
Create any new testing artifacts directly in Test Manager. You can work from Test Manager or by using the native Test Manager integration with CLI and CI/CD extensions.
More details are available in the linked documentation.
Test data queues and the test data queue activities are also removed as of July 31, 2026. Use Data Fabric / Data Service instead.
Can I still migrate testing objects from Orchestrator to Test Manager?
No. The migration tool was available starting with June 25, 2025, but remaining test artifacts can no longer be migrated to Test Manager since the removal on July 31, 2026.