Introduction
The ability to trace the linkages from requirements all the way to defects or vice versa is particularly useful in a software release cycle. In fact, it can have special meaning at various phases in that release cycle. For example, starting with requirements, knowing how many of them have tests written for them is useful in the early stages to ensure appropriate test coverage. Once the software has been built, keeping track of which test executions have passed for a particular requirement allows the team to make a quality statement about these requirements. And then keeping track of how many open defects exist for requirements help make a Go/No-Go decision regarding the readiness of the software to be shipped.
...
Another very important reason to run a Defect to Requirement traceability report is to get a better sense of how many defects are holding up requirements and more importantly, which defect(s) is impacting the most number of requirements – thereby allowing for better bug-fixing prioritization.
...
Traceability in Zephyr for JIRA can be accessed from the top menu (screenshot capture10) or from the “Tests” menu in the Project sidebar
...
| Tip | ||
|---|---|---|
| ||
: In order to get useful traceability reports, ensure the following during test creation and execution:
|
...
Types of Traceability Reports
...