In this article we will learn the fundamental concepts on tracing (mapping) the requirements to the other software artifacts or deliverables in the SDLC model and how to leverage HPQC for mapping the tests to the requirements.
There are two options to do this.
- When you enter a requirement in the “Requirements” module, you can link it to a test through “Test Coverage” sub module, provided a relevant test exists.
- When you write a test in the “Test Plan” module, you can link it to a requirement through “Req Coverage” sub module, provided a relevant requirement exists.
Option 2 explained in detail (i.e., mapping tests to functional requirements in “Test Plan”)
Step 1. In the Test plan, navigate to the required test for which you need to map the requirement.
Step 2. Select “Req Coverage” tab.
Step 5. There are four ways you can map a requirement to the selected test
a. Right click and select “Add to Coverage (Without Children)” from the pop-up menu
c. Hold left mouse control and drag the requirement on to the coverage grid. (Coverage Grid is the space containing “Entity Name” and “Req Description”
d. Double click the requirement.
Best Practice: Enter the requirements into HPQC first, write tests relevant to those requirements and use option 2 to link each of the tests to the relevant requirements.
- Use the “Add to Coverage” arrow and choose “Add to Coverage (Include Children)” to add the requirement, in situations where you are sure that a single test can be mapped to a requirement group. (e.g., if there is a requirement group called “Authorised User Requirements” which will have two sub requirements such as, login to the Order Management System and create an order, then a test called “Authorised User Test” can be mapped to the entire requirement group).
- By default, the coverage is possible for the following requirement types: Functional, Testing, and Undefined.