Automated Test Traceability for Jira
In the world of Agile, DevOps, CI/CD, and any other industry word we want to throw in the mix, developers and testers are under enormous pressure to quickly deliver high quality, functional software. Requirements must be backed by a series of tests, so that there is visibility into whether assigned requirements have been fulfilled. Many organizations associate test results with requirements manually in Jira (or other platforms), but this can be tedious and a waste of effort.
Instead, developers and testers can automate testing, and in turn rely on a clear, consolidated dashboard in which they have visibility into:
- all test results and the percentage of tests passing and failing, and
- what percentage of requirements in scope for the current release have passing tests associated with them.
Parasoft’s Development Testing Platform does just this – the screenshot below shows an example of its consolidated dashboard for test reporting and requirement traceability:
So how do we put this to use?
One critical piece in the automation puzzle is the ability to link specific tests to requirements. An application tester may have a test that they can automate with specific inputs and outputs, but without linking it to specific requirements, they are still wasting time. Using automation from Parasoft SOAtest, application testers can create automated tests linked to specific requirements in a tracking system, such as Jira, and then quickly view top-down reports within the Development Testing Platform.
To do this, simply attach an @req type and enter the correlating id from Jira, as shown below:
Now that you’ve linked the test with a requirement tag, it can be traced after automated test execution. When the test is invoked from a continuous integration tool, like Jenkins, a report is generated that contains the @req type and references it back to the requirement in Jira.
This information can also be consumed inside the Development Testing Platform to give developers, testers, and managers a powerful, central point of reference for how thoroughly requirements (in scope of the current release) are being covered by tests. Requirements that are untested (or which have failing tests) can be quickly identified and resources can be diverted to fix the problem. In Parasoft’s Development Testing Platform, this looks like the below:
And there you have it – a holistic overview that quickly shows you whether or not tests have passed for each requirement.
To get more information about the technologies used, follow the links below: