Traceability Analysis - Key To A Better Quality Software - Qmetry

Traceability Analysis – Key To A Better Quality Software

Agile , Atlassian , Defect Tracking , Differentiators , Key Features , QA , QA to QE , QMetry , Software Testing , Test Management Tools Aug 26, 2016

Continuing from where we left in my last blog; test coverage is an important metric to avoid software glitches and a step in right direction to build quality software.  To reinforce the quality momentum achieved by test coverage; traceability is the level-up tool providing visibility by tracing the defect to its root location and cause.

For Agile projects; tracing the defect path from Test Execution / Release/Build all the way upto Requirement/Story is crucially important.  Also, maintaining the track per test run helps in recording progress.

QMetry Test Management For Jira provides Traceability reports in Mindmap format.  Visually; it is a tree structured report and very simple to comprehend.  Although; it is very powerful tool to achieve quality.

Planning for Traceability:

Creating test scenarios covering positive, negative, performance and ancillary tests is the first step towards Traceability.  By following simple process that includes enough number, depth and breadth of tests; Traceability can be secured.  Based on test coverage planning, one can define sufficient number of tests to each feature to fully cover all the scenarios.

The test coverage analysis is a way to examine what parts of the logical structure of a program is covered during test execution. The logical structure depends on the code coverage metric being used. For example, Dynamic Dataflow coverage looks at what parts of the data flow have been exercised. Different test coverage metrics verify code from multiple angles, the common goal is to provide meaningful insight into how much code is tested and which parts have been already executed.  Traceability provides the path to defect and helps in identifying root cause.  Thus, a well defined; test coverage followed by traceability can lead to concrete defect prevention and resolution.

Traceability can be hard to do without proper tools.  While spreadsheets are effective for simple traceability for small projects; it is whole different challenge for projects with hundreds & thousands of use cases, many test scenarios and multiple stories.  Spreadsheets and simple tools fall flat in giving full traceability resulting in defects remaining untraced. The finer breakdown of trace relationships and managing increasingly complex multi-layered reports is effectively managed by test management tools like QMetry Test Management for Jira.

Although, moderation is key here. Test Management Tool like QMetry which supports traceability can also lead to tendency in testers to go overboard by tracing everything. It can lead to unnecessary efforts with very little tangible outcome.

To conclude; by planning the test coverage and traceability beforehand and then monitoring them through very granular reports of test management tool like QMetry Test Management For Jira; defects can be discovered and traced rapidly and to the root cause.  This leads to defect prevention and thus resulting into high quality software.

Deepak Parmar

Deepak Parmar

Get all Latest QA Updates in Your Inbox

No sales pitches, no games, and one-click unsubscribe.

By submitting this form, you agree that you have read and understand QMetry’s Terms and Conditions.
You can opt-out of communications at any time. We respect your privacy.