Preguntas frecuentes: obsolescer el módulo de pruebas

Esta página de Preguntas frecuentes (FAQ) proporciona respuestas sobre la obsolescencia del módulo de pruebas de Orchestrator y sus implicaciones.

Consulta la línea de tiempo de Obsolescencia para comprobar los detalles cronológicos de este cambio.

¿Qué significa "paridad de características"?

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.

¿Qué cambios inmediatos son necesarios?

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.

¿Cómo se debe elaborar una estrategia para el trabajo de prueba futuro?

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.

¿Cómo afecta esta obsolescencia al trabajo de prueba?

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.

Can I migrate testing objects from Orchestrator to 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.