- 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
- Orchestrator testing
- FAQ - Deprecating the testing module
- Test Automation
- Testing Data Retention Policy
- 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 will achieve feature parity by March 31, 2025.
Until Test Manager equals the functionality of Orchestrator's Testing tab in March 31, 2025, no immediate changes are needed. After that date, you need to move your test artefacts to Test Manager. We will provide a migration tool to easily move your test artefacts.
While your existing testing artifacts remain unaffected until March 31, 2025, we encourage you to create new testing artifacts in Test Manager to minimize future migration work after March 31, 2025.
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.
Starting with March 31, 2025, you can migrate specific testing objects from Orchestrator to Test Manager. Once Test Manager achieves feature parity with the Testing module, you will have six months to move your testing objects from Orchestrator to Test Manager.
