Our documentation site has been updated to AIO Tests Knowledge Base

Traceability Detail Report

Owned by Noopur Varshney [AIO Tests]
Last updated: Feb 16, 2023
3 min read

A traceability report is used to track if all the requirements have been mapped to cases which in turn ensures that the product is being tested thoroughly. AIO Tests has an inbuilt end-to-end traceability report that shows requirements mapped to cases, executions and defects. Requirements from multiple projects can be specified as an input to the report for cross-project visibility. Similarly, defects from multiple projects are displayed in the report if they are linked to runs of the project being viewed.

Generating Traceability Detail Report

Click on the right chevron next to the Traceability Detail report to get the input screen for the report.

 

The input screen has the following fields:

  • Requirements: Specify the requirements for which the report needs to be generated. One or more requirement(s) can be specified via three options (requirements from multiple projects if linked with cases of the project can be specified)

    • List: search list of Jira issues via key or title. Users can filter the list by project name & Jira issue type

    • JQL (Jira Query Language): specify requirements meeting a criteria using standard JQL. Clicking on the JQL box opens up the standard Jira box which helps in faster JQL creation

    • Filter: select a filter created and saved in Jira (the list of filters from Jira is pre-populated and is shown upon clicking inside of the search box)

  • Include Child Issues: Selecting this checkbox will include the child issues of all the specified requirements. E.g. if the specified requirement is an Epic with multiple stories, all the stories don’t need to be specified separately if this option is checked. If not selected, only the parent issues are displayed in the report

    • Filter Child issues: Clicking the icon will allow users to specify which issue types to include in the report (e.g. user might only want to see stories not task/sub-tasks so in the dropdown user can select Story)

  • Cycles: Specify which execution cycles should be considered for traceability of the selected requirements; multiple cycles can be specified. If all or any of the check boxes under Cycles are selected, cycles list will need to be provided

  • Retrieve Runs: Check this box to see the test execution results in the traceability report. If not selected, execution details will not be displayed in the report

  • Retrieve Defects: Check this box to see the test execution defects in the traceability report. If not selected, defect details will not be displayed in the report

  • Include only last Run: Check this box if only the last run of the cases should be considered for the report. If not selected, all runs of the resulting cases will be shown in the report

**By default, all check boxes are checked**

Click Generate to view the report.

Sample report shown below for our ATM project

The below screenshot is when traceability report is generated via JQL and cycles have not been specified.

 

The report shows two columns - Requirement and the Cases that are mapped with the requirements.

  • Requirements are shown with a hierarchy as “Include child issues” was selected. The column also shows the current status of the requirement in Jira and it’s priority

  • Cases are shown with their status

 

The below screenshot is the report output when cycle 'ADP-CY-1' has been specified along with ‘Retrieve Runs’ and ‘Retrieve Defects’ check boxes selected and ‘Include only last run’ checkbox not selected. The report now shows 4 columns - Requirement, Cases, Test Execution Results and Defects.

  • Requirements and Cases are same as above

  • Test Execution Results column shows the execution status, execution date, who executed it and if multiple runs have been created, they are also shown

  • Defects column shows associated defects and their status and priority in Jira