Page Comparison

Using this feature you can export a set of Requirements Test Cases from one project to another. This feature is useful from Requirement Test Case re-usability perspective as well. Please see (reference) #1 at the bottom of this page.

Overview of Implementation

1. The operation will create a new Id for Requirements Test Cases in the new project.
2. System will maintain link to source requirement Test Case in the back end.
3. The hierarchy will be preserved, depending upon the user preference.
4. The attachments will also be copied.
5. Regarding the links / relationships, system will provide an option to select the ones desired to be carried over to the exported entity.
6. If another copy of a requirement Test Case already exists in the target project, the system will return an error.

7. In the case of iterative export of a second requirement Test Case in the same hierarchy, the system will

   • consider hierarchy as a container and perform checks only at the leaf level.

   • So a second requirement Test Case will append another hierarchy in the target project.

User Interface

1. Notes and Recommendations
   1. It is highly recommended that all the desired requirements Test Cases should be exported in one single operation. It is easier to delete a requirement Test Case in the target project than iterating through the process.
2. The requirements Test Cases export process is described below:
   1. Use multi-select to select all Requirements Test Cases you wish to export.
   2. Choose "Export RequirementTest Case" from the Table Menu.
   3. When prompted , enter the name of target project
   4. Make your choice, and choose "Export".
   5. The selected requirements Test Cases and their hierarchy will be appended to the Planned Requirements Test Cases table of target project.

...

...