- 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
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Orchestrator testing
- FAQ - Deprecating the testing module
- Test Automation
- Testing Data Retention Policy
- Resource Catalog Service
- Authentication
- Integrations
- Classic Robots
- 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 on March 31, 2025.
Until Test Manager equals the functionality of Orchestrator's Testing tab on March 31, 2025, no immediate changes are needed. After that date, you need to move your test artefacts to Test Manager.
While your existing testing artefacts remain unaffected until March 31, 2025, we encourage you to create new testing artefacts 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.
