- Getting Started with Test Suite
- Studio
- Orchestrator
- Orchestrator
- Testing in Orchestrator
- FAQ - Deprecating the testing module
- Testing robots
- Test Manager
Test Suite 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 6, 2025.
Until Test Manager equals the functionality of Orchestrator's Testing tab in March 6, 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 6, 2025, we encourage you to create new testing artifacts in Test Manager to minimize future migration work after March 6, 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 6, 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.
