- Test Suite 入门
- Studio
- Orchestrator
- Orchestrator
- 在 Orchestrator 中进行测试
- 常见问题 - 弃用测试模块
- 测试机器人
- Test Manager
常见问题 - 弃用测试模块
此常见问题 (FAQ) 页面提供了有关 Orchestrator 测试模块的弃用及其影响的答案。
请访问弃用时间线,以按时间顺序查看此更改的详细信息。
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.