Using this feature you can export a set of Test Cases from one project to another. This feature is useful from Test Case re-usability perspective as well. Please see (reference) #1 at the bottom of this page.
Overview of Implementation
- The operation will create a new Id for Test Cases in the new project.
- System will maintain link to source Test Case in the back end.The hierarchy will be preserved, depending upon the user preference.
- The attachments will also be copied.
- Regarding the links / relationships, system will provide an option to select the ones desired to be carried over to the exported entity.
- If another copy of a Test Case already exists in the target project, the system will return an error.
consider hierarchy as a container and perform checks only at the leaf level.
So a second Test Case will append another hierarchy in the target projectOnly one version of the Test Case will be copied.- System will preserve the Committed / Un-Committed state of the Test Case.
User Interface
- Notes and Recommendations
- It is highly recommended that all the desired Test Cases should be exported in one single operation. It is easier to delete a Test Case in the target project than iterating through the process.
- The Test Cases export process is described below:
- Use multi-select to select all Test Cases you wish to export.
- Choose "Export Test Case" from the Table Menu Bar.
- When prompted , enter the name of target project
- Make your choice, and choose "Export".
- The selected Test Cases and their hierarchy will be appended to the Planned Test Cases table Table of target project.
In the case of iterative export of a second Test Case in the same hierarchy, the system will