- 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 - Migrating test artifacts to Test Manager
- Test Automation
- Testing Data Retention Policy
- Resource Catalog Service
- Authentication
- Integrations
- Classic Robots
- Troubleshooting

Orchestrator user guide
FAQ - Migrating test artifacts to Test Manager
The deprecation of the Testing module in Orchestrator requires you to migrate objects from Orchestrator to Test Manager. Test Manager provides extended capabilities to what Orchestrator currently offers. To use the full potential of Test Cloud, we recommend you to migrate objects into Test Manager.
You must initiate the migration yourself and decide which test sets go into which project. Test Manager provides test projects, allowing for a more granular organization of your testing efforts, whereas Orchestrator groups tests using folders.
- New test cases are created in Test Manager, if they do not exist.
- Existing test cases are referenced to the new test sets in Test Manager.
- The test results of the specific test set are migrated, and corresponding test set schedules are created, but in a disabled state. You will need to manually enable these schedules.
No, you must have access to the folder where the Orchestrator test set is located, to migrate it.
For now, test data queues will remain in the Orchestrator Testing module, with the same functionality as before.
The duration of the migration depends on the number of artifacts you need to migrate. For instance, processing 1000 logs each with an attached screenshot would require more time than handling 1000 logs without screenshots.
- What is the purpose of the migration?
- Do I need to trigger the migration or will it be done automatically?
- What objects do I need to migrate?
- Can I migrate Orchestrator test sets, regardless of access?
- Can I re-migrate a test set?
- What happens to test data queues?
- How long will it take to migrate 100 test sets in a project?
- Will I get a notification when the migration of a test set is completed?