Continuous Testing Server with Functional UI test execution in parallel
BuildWise supports an easy way to generate requirement (to functional test) traceability matrix, in seconds.
Understand Requirement Traceability first
Traceabilty (requirement to) to code level is wrong, a complete waste of time in agile projects. Code refactoring happens all the time, using Refactoring tool support in IDE, thousands of lines of code change may occur in minutes (without affecting the external behaviour).
The only meaningful of traceability is requirement => functional test, as a functional test verfies a user story (requirement) functionally.
Be realistic with Requirement Traceablity
“I have, in 30 years in the business, in industry, research and a little bit in government, NEVER seen a traceability matrix pays off.” - Alistair Cockburn, a cu-author of The Agile Manifesto
“My experience is that traceability matrices are highly overrated because the total cost of ownership (TCO) to maintain such matrices, even if you have specific tools to do so, far outweigh the benefits” - Scott Amber, renowned author of a number of agile books.
How to enable requirement traceability in functional test scripts?
Our approach is simple, just append user story IDs in the test case name, wrapped in a pairt of ‘[’ and ‘]’.
Generate Requirement Traceability with easy in BuildWise
Navigate to a project setting page, click ‘User Stories’ button
Upload user stories CSV
The same CSV is provided, very simple. It shall very easy to create from an export from JIRA.
Geneerate Requirement-Test traceability
Click ‘Refresh Traceability Matrix’ button, and click ‘Generate’ button
The coverage (%) is shown at the top, and you may view test script (content) associated to each user story.
Export Requiremnt Traceability Matrix
Click ‘Export Excel’ button to export a traceability spreadsheet.