Linking test script steps to requirements in the Requirements Management application
If you have test scripts that fulfill multiple
requirements, you can link a test script step to one or more requirements.
Before you begin
- Link a Quality Management project to a Requirements Management project.
- Add test scripts to a test case that has associated requirements.
- By default, linking between test script steps and requirements is not enabled. To display the linked requirements in the Attachments/Links section of the manual test script editor, see Setting test script preferences for requirements management.
Limitations:
- If configuration management is enabled for your project, the current configuration must be a global configuration to link to artifacts such as requirements or development plans in other Collaborative Lifecycle Management (CLM) applications. For more information, see Getting started with configurations in CLM version 6 releases.
- If you have not enabled configuration management, when you create a link to external artifacts in a CLM application, a link is automatically created back to the source artifact in the target application, which is called a back link. However, the synchronization between bidirectional links and the traceability between source and target artifacts are not guaranteed.
Learn more about bidirectional links: When a source artifact and target artifact link to each
other, this is known as bidirectional linking. The source and target applications store their links
in separate databases, and the source application does not have access to the database in the target
application. Certain transactional operations, such as when artifacts are copied or deleted, can
occur on the source application server. In these cases, corresponding back links in artifacts in the
target application are not automatically added or removed. Also, instances occur where back links
are intentionally removed from the target application without removing the corresponding link from
the source application. As a result, if bidirectional links are not in a state of synchronization,
traceability between the source and target artifacts can appear different based on your starting
viewpoint.
Procedure
- To link a single step to a requirement that is
associated with the parent test case:
- From the manual test editor toolbar, click the Show
Requirement View icon (
) to open
the Requirement View. - In the Requirement View, select one or more requirements, and then click the Add Requirement
Link icon (
). The linked requirement is shown in the attachments and links column. Alternatively, drag
the requirement link from the panel to the attachments and links column.
- From the manual test editor toolbar, click the Show
Requirement View icon (
- To link a step to any requirement that is associated
with the project:
- In a step, click the Action Menu icon (
), and then click Link to any Requirement. - In the Links window, select a requirement from the Requirements Management project that is linked to this project.
Tip: If you want requirement links in a test script to be automatically copied to the Requirement Links section of a parent test case when you add an existing test script to the test case, you can enable the Copy Requirement links into Test Cases when adding new child Test Scripts option in Test Scripts Preferences.When this preference is enabled, it also applies to a requirement link added to a step by using the Open Services for Lifecycle Collaboration (OSLC) QM API. In this scenario, a link is automatically created from the test case to the requirement that was linked to the test script step.
- In a step, click the Action Menu icon (
Results
What to do next
|
Jazz.net channel User Education channel |
Agile learning circle Learning circles |
developerWorks forums |
Deployment wiki Support blog |
