Traceability ensures tracking in real-time of information flows and linkages. It is especially useful for Agile teams that use products like Jira to establish forward and backward traceability through the development lifecycle.
For Agile teams using Jira for test management, a tool such as QTM4J helps establish traceability and enhances:
Here's how you can use traceability inside Jira with QTM4J
Users can trace the linkage of stories with a test case by viewing which Jira stories are linked to an asset. To do this, they need to open the test case detail page in QTM4J and go to the Story tab. The story tab shows a list of the stories to which the current test case is linked. One can also select a particular version from the dropdown to view the linkages with stories. Using the Jira issue page, testers can associate the test case to the relevant Story and if needed also link or unlink the stories from the story tab for a test case detail page. Users can link either a single test case to story from the page or multiple test cases with the bulk operations feature on the test case list view.
Traceability Reports in QTM4J are designed to enable testers to establish a relationship among requirements, test cases, test cycles and defects. Take any specific test artefact and discover the web of its relationship with other artefacts. QMetry’s Traceability Reports enable users to understand the hierarchy of issues and flexibility to drill down to the level for details along with organized and detailed information.
By using traceability reports, agile teams can manage the quality of their projects more efficiently as managers and team leads can understand if the requirements are covered. This eliminates the chances of poorly maintained test libraries and one can anticipate and deal with changes int the requirements. One can also ensure that changes are replicated across linked test cases.