Table of Contents
Traceability tracking is used to ensure the completeness and thoroughness of the testing process by tracing requirements with test cases, test cycles, test plans, defects and execution results. Establishing traceability tracking for each requirement will ensure that it's coverage for at least one test case. Coverage reports make it easier to identify orphan requirements or test cases if any. For example, it is common practice to demonstrate that a requirement is verified by test artifacts in order to know the status of those items at each step of the product development process. One great benefit to traceability tracking is the ability to assess the impact of your requirements. When requirements change through a project, a traceability report allows you to identify all of the impacted artifacts. As a result, you are able to quickly assess the impact of the change and act accordingly.
In the Issue view page, under the section "Traceability", you can manage the traceability links between the issue and test artifacts, such as test cases, test plans, and test cycles.
Click on the arrow icon to create or add existing test artifacts to the issue. You can also add test artifacts from other Jira projects.
Once you're finished, you can see all test artifacts under the "Traceability" section. You can also configure the display behavior of the "Traceability" section, learn more here: Hiding traceability sections.
TM4J offers forward and backward traceability between Jira issues and test artifacts. From the test case, test plan and test cycle screen you can see and manage the traceability link with Jira issues. TM4J also support traceability links with Confluence pages and any external tool via Web Links.
The coverage report allows you to track the test coverage in a simple two columns table. You can either filter the report by test cases or by Jira issues.
The traceability report allows you to track the traceability in a multi-column table. You can either filter the report by test cases or by Jira issues.
The traceability tree report allows you to track the traceability between issues and test artifacts in a tree view. You can input a JQL search or a favorite filter from Jira to specify the first hierarchy level you want to inquire on. This first-level filter is the only one required to generate the report, though additional levels may be added via Additional Hierarchy Levels.
The matrix report allows you to track the test coverage in a two levels matrix. You can either filter the report by test cases or by Jira issues. The colors in the cells mean the last test execution result of a test case.