Linking test script steps to requirements in Rational DOORS

If you have test scripts that fulfill multiple requirements, you can link a test script step to one or more requirements.

Before you begin

  1. Integrate IBM® Rational® Quality Manager with IBM Rational DOORS® Version 9.4 or later by using Open Services for Lifecycle Collaboration (OSLC).
  2. Link a Quality Management project to a DOORS requirements project.
  3. Add test scripts to a test case that has associated requirements.
  4. By default, the Validates column in the test script editor that you use to link requirements to test script steps is disabled. To turn on the Validates column in the Manual Steps table, see Setting test script preferences for requirements management.
Limitation: When you create a link to external artifacts in a CLM workbench source application, a link is automatically created back to the source artifact in the target application, which is called a back link. However, a state of synchronization between bidirectional links and the traceability between source and target artifacts are not guaranteed.
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 in the source application server. In these cases, corresponding back links in artifacts in the target application are not automatically added or removed. There can also be instances where back links are intentionally removed in the target application without removing the corresponding link in 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 differently based upon your starting view point.

Procedure

  1. Open an existing test script (Construction > Browse > Test Scripts) or create a new test script (Construction > Create > Test Script).
  2. If the attachments and links column is not shown, click the Show/hide Contents icon; then select the Show Attachments/Links check box.
  3. To link a single step to a requirement that is associated with the parent test case:
    1. From the manual test editor toolbar, click the Show Requirement View icon (Show Requirement View) to open the Requirement View.
    2. In the Requirement View, select one or more requirements; then click the Add Requirement Link icon (Add Requirement Link). The linked requirement is shown in the attachments and links column. Or, drag the requirement link from the panel and drop it in the attachments and links column.
  4. To link a step to any requirement that is associated with the project:
    1. In a step, click the Action Menu icon (Action menu drop down); then click Link to any Requirement.
    2. 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.
  5. Click Save.

Results

Linked requirements are displayed in the Validates column of the table. In the Rational DOORS application, links are created from the linked requirement to the test script artifact, not to the individual test script steps.


Have a problem or a question? Post it in the Jazz.net forum.