- 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
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Business Rules
- Storage Buckets
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator user guide
FAQ - Deprecating the testing module
This Frequently Asked Questions (FAQ) page provides answers regarding the deprecation of Orchestrator's Testing module and its implications.
Visit the Deprecation timeline to check the chronological details of this change.
Feature parity refers to mirroring the capabilities of Orchestrator's Testing module in Test Manager, making the transition seamless, while minimizing the loss of functionality. Moreover, no additional features will be added to the Testing tab. Our deprecation timeline indicates that Orchestrator and Test Manager achieved feature parity on April 18, 2025.
Use the following migration tool to move your test artifacts: Importing Orchestrator test sets.
Before leveraging the migration tool, we recommend you prepare in the following ways:
- Ensure you have the required licenses to access and work with Test Manager. For more information, visit Licensing Test Manager.
- Assess your specific needs and
create a plan for how to group your Orchestrator test sets into specific
projects within Test Manager.
Note: Note that in Test Manager projects are used to organize testing. Orchestrator does not have this kind of structural concept, therefore it is not necessary to group existing artifacts from Orchestrator into Test Manager projects.
- You will be able to use test sets to transfer test artifacts. You can designate which test cases and test results go to which Test Manager project by importing the corresponding test set. If there are Orchestrator test cases that are not part of a test set, group them into a test set before importing into Test Manager.
- Test data queues and CI/CD integrations: These will not be migrated but their functionality will remain unaffected.
For more information regarding migration, visit FAQ - Migrating test artifacts to Test Manager.
While your existing testing artifacts remain unaffected until the release of the migration tool, we encourage you to create new testing artifacts in Test Manager to minimize migration work.
Automated executions will continue to run via Orchestrator. The only difference is that test cases, test sets, and results will be managed in Test Manager.
Yes, use the following migration tool to move your test artifacts: Importing Orchestrator test sets. From the moment the migration tool is released, you have six months to move your testing objects from Orchestrator to Test Manager.
