Traceability from Jira Issues
Traceability is one of the most sought-after KPIs from a testing perspective. AIO Tests has multiple ways of viewing and achieving end-to-end traceability as well as reporting on it - linking and viewing cases for a requirement in Jira, linking defects with case executions, viewing impacted cases from a bug, and viewing issues/defects with their status in Jira. Traceability Summary and Traceability Detail Reports allow to visualize traceability from requirements perspective.
In this documentation, you’ll understand:
Traceability from Jira Issue View
AIO Tests allows you to integrate with Jira via the AIO Tests Jira Panel effortlessly. By integrating AIO Tests into the Jira issue view, you can not only view traceability information of a Jira issue without leaving Jira, but can also link test cases directly to Jira issues and track testing progress seamlessly. AIO Tests panel shows four tabs in the Jira Panel - Cases, Cycles, and Impacted Executions/Defects. Users can:
create and link cases
view latest and previous executions
quickly execute a case and much more.
For more detailed information on the AIO Tests Jira Panel, click here.
Traceability Reports
AIO Tests allows you to view the coverage of the requirements and end-to-end traceability via its Traceability Summary report. Through this report, you can not only view the coverage of specific requirements, but you can also view the respective testing status, and check for defects. For more information on the traceability summary report, click here.
If you want to view end-to-end traceability for the specified requirements, you can do it with a Traceability Detail report. This report shows requirements mapped to cases, executions and defects. For more information on the traceability detail report, click here.
For further queries and suggestions, feel free to reach out to our customer support service via help@aiotests.com.