- Premiers pas avec Test Suite
- Studio
- Suite de tests - Studio
- Vue d'ensemble (Overview)
- Activités et API de test
- Orchestrator
- Orchestrator
- Test dans Orchestrator
- FAQ - Obsolescence du module de test
- Test Manager
FAQ - Obsolescence du module de test
Cette page de questions fréquemment posées (FAQ) fournit des informations concernant l’obsolescence du module de test d’Orchestrator, ainsi que sur les conséquences de cette obsolescence.
Consultez la chronologie d’Obsolescence pour prendre connaissance du calendrier de ces changements.
Feature parity refers to mirroring the capabilities of Orchestrator's Testing module in Test Manager, making the transition seamless. 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 January 31, 2025.
Until Test Manager equals the functionality of Orchestrator's Testing tab in January 31, 2025, no immediate changes are needed. After that date, you need to move your test artefacts to Test Manager.
While your existing testing artifacts remain unaffected until January 31, 2025, we encourage you to create new testing artifacts in Test Manager to minimize future migration work after January 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 January 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.
