Viewing Traceability on asset level with QMetry Test Management for Jira (QTM4J)

Traceability allows product teams to get complete visibility about the testing of the product features. In an application development life cycle, the stories are first documented and then implemented in the product. Test cases are written to test the stories. These test cases are planned, executed in test cycles and the bugs then discovered are linked to those test case executions. During this process, a daily review of the project or its releases happens in the scrum or internal meetings. At this point, a report or document is referred to check the daily progress which could be a traceability report.

Benefits of Traceability in product testing

• Ensure requirements for a feature or product that is being tested with their relevant test cases.
• Identify the features that are missing or have defects and resolve them before the release.
• Ensures sufficient documentation of requirements and their test cases for future reference, improvements possible, and assist with their testing.
• Easy to update and maintain test cases when requirements change.
• Simplifies defect triage and planning in case of larger backlogs.
• Confirms complete test coverage of all the requirements.

QTM4J helps to manage the requirements and makes it easy to get their traceability leading to improved efficiency and coverage.

To get this traceability, the test cases should be linked to a story in Jira, to ensure proper coverage of its features to be tested. The story is then added to a test cycle to automatically plan its linked test cases for execution in that cycle. Once the test cases are executed in the test cycle any defects found at the time of the testing should be linked against those test cases. Let us see how we can view the traceability at different levels.

View Traceability Story to Test Case, Test Execution, and Bug

The primary goal of the testing process is to verify the features specified in the requirements and identify the defects discovered during test execution. Using the QTM4J app, the project managers can get the traceability of test cases that are related to the requirement from the ‘Test Case/Acceptance Criteria’ section in the Story. The list of the test cases to be executed in the scope of the story are listed on the story page itself along with the step details and their sequence for execution.

All the executions of the linked test cases can be tracked from the Executions tab of the test case linked with the story. This helps to view the status of that test case version in all the test cycles, and also shows the identified defects linked to the test cases. Other execution details like environment, builds, executed date, tester, etc. are also available. These details can be quickly accessed from the Story page > Test Case/Acceptance Criteria > Test Case > Executions tab.

Traceability from Test Case to Test Cycle and Story

Based on the testing scope, a test case may be executed several times in different test cycles for multiple combinations of builds, environments, iterations, and these executions may have different results along with associated defects. All test case traceability to test cycles and defects are visible on the Test case execution tab of the test case details as per the selected test case version.

QA managers can quickly view all the stories that get covered by the current test case version and also link additional stories relevant to the test case from its “Story “tab.

Traceability from Test Cycle to Test case and Story

It is very important for QA managers and testers alike to know how many, and which stories got impacted due to the test cases that failed during a test cycle execution. This helps them plan the fixes for those defects logged against the failed tests sooner for a successful release of a feature. Also, this view helps to know if the failures are specific to a certain build or environment. This information is available from the Test Cycle > Test Cases tab.

The stories being covered by the test cycle are quickly accessible from the “Story” tab.

Traceability from Test Plan to Test Cycle

For a scrum master or a QA manager, this is one perfect view to check the testing progress of a release. The below view shows the test plan for the release listing all the test cycles in the release, their aggregate execution status, count of test cases in them, and the defects linked.

Defect/Bug Traceability

When it comes to defects/bugs, knowing their source is really important.

• A tester would want to automatically record the details of the test case version/test step, environment, build for which the defect is raised. While retesting the issue tester would be interested to have the test execution traceability available to quickly reach the execution run and perform the steps. Also, the tester would want to view the traceability, impact, and historical data of the defect for different combinations of environment, builds, and other execution details.
• A developer who is fixing the defect would also be similarly interested in the details of the test case version/test step, environment, build for which the defect is raised.

All these above details are covered by the QMetry Bug traceability section present on the Bug issue detail page, as shown below.

Traceability Report

We believe any reporting without the detailed traceability presented by QMetry would be incomplete. The QA Managers, Scrum Masters, and Product Managers refer to the traceability

report during their daily scrums, sprint reviews, or any testing progress meetings at a given point in time to review the readiness/completeness of a user story. The traceability report displays overall end-to-end traceability from Requirements >> Test Cases >> Test Executions >> Bugs and their current workflow status. This report is most loved by all the QMetry customers.

The entire flow of this traceability will be available in the Traceability Report in the QMetry for Jira app. This traceability can be viewed by Test Case, by Requirement, or by Defect and may be filtered further by requirement, test case, test cycle, execution, test plan, or defect.

If you want to see QTM4J in action, try for free.

Page source:https://www.qtm4j.com/blog/viewing-traceability-on-asset-level-with-qmetry-test-management-for-jira-qtm4j