As we saw in Chapter 3, Understanding Components of Testing with Jira, the traceability matrix is useful for obtaining a clear understanding of the project progress and identify requirements that demand more testing efforts or have more defects. The traceability matrix also indicates the test strategy, the type of test activity, and the tasks that have been defined and planned by test professionals to verify stated requirements. This gets created early in the phase so that it can be reviewed by project stakeholders, which affords sufficient time to monitor it, provide feedback, and adjust the test process as required by the team to achieve the test goal.
Establishing relations between the requirements and the test plan is the first part of creating the traceability matrix. Whenever a requirement ticket is created in Jira, test professionals can prepare a test plan ticket and link it to the requirement. One requirement may have...