Setting test script preferences for requirements management

You can set a preference for whether test script steps can be linked to requirements in the manual test script editor. When this preference is enabled, the Validates column is displayed in the manual test script editor, and it lists any requirements that are linked to steps. You can also enable a setting to automatically copy the associated requirement links from test scripts to their parent test cases when you add the test scripts.

Before you begin

Link a Quality Management project to a Requirements Management project.


  1. Click Administration > Manage Project Properties.
  2. In the Properties navigation menu, click Test Script Preferences.
  3. You can link single steps or multiple steps to requirements. To display the linked requirements in the Attachments/Links section of the manual test script editor, select Allow linking between Requirements and Test Script steps.
    Linking from test script steps to requirements is enabled.
  4. When you add existing test scripts to a test case, the test scripts might have steps that are linked to requirements that they validate.
    To enable a preference so that the requirement links from the test scripts are automatically copied to the parent test case, select Copy Requirement links into Test Cases when adding new child Test Scripts.
    Note: When this preference is enabled, it also applies to a requirement link that is 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.
  5. Click Save.
    Limitations: If you do not enable configuration management, when you create a link to external artifacts in the Engineering Lifecycle Management application, a link is automatically created back to the source artifact, which is called a back link. However, the synchronization between bidirectional links and the traceability between source and target artifacts might be unavailable depending on certain transactional operations in the source or target application.