Orchestrator 用户指南
常见问题 - 弃用测试模块
此常见问题 (FAQ) 页面提供了有关 Orchestrator 测试模块的弃用及其影响的答案。
请访问弃用时间线，以按时间顺序查看此更改的详细信息。
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 achieved feature parity on April 7, 2025.
Until Test Manager equals the functionality of Orchestrator's Testing tab on April 7, 2025, no immediate changes are needed. After that date, you need to prepare for migrating your test artifacts to Test Manager. We will provide a migration tool to move your test artifacts. Only after the migration tool release, you can start moving your test artifacts.
Before leveraging the upcoming migration tool, we recommend you prepare in the following ways:
- Ensure you have the required licenses to access and work with Test Manager. For more information, visit Licensing Test Manager.
- Assess your specific needs and create a plan for converting your Orchestrator test sets into specific projects within Test Manager.
Note: Note that Test Manager and Orchestrator have different structures for managing test artifacts.
- You will be able to use test sets to transfer test artifacts. You can designate which test cases and test results go to which Test Manager project by importing the corresponding test set. If there are Orchestrator test cases that are not part of a test set, group them into a test set before importing into Test Manager.
- Test data queues and CI/CD integrations: These will not be migrated but their functionality will remain unaffected.
While your existing testing artifacts remain unaffected until the release of the migration tool, we encourage you to create new testing artifacts in Test Manager to minimize migration work.
