Shows a normalised horizontal stacked bar chart with the current Requirement coverage for the selected Analysis Version (or Test Plan), Test Environment and Grouping field.
Please note
To be able to use this report your project must have Requirement Coverage enabled. See how in Configure JIRA project to be used as Requirements project.
Aim
In order to analyze the current status of your release, or even other releases from the past, you need to evaluate the status of requirements, taking into account the respective results.
You might want to analyze just the requirements implemented in a given version or you may want to analyze requirements from earlier versions based on your regression testing.
The overall requirement coverage report provides the means to analyze your requirements statuses in real-time.
How to use
This report is either accessible from "Xray Reports" icon on the project left side bar or from the standard "Reports" icon, which includes other kind of reports besides Xray.
You need to configure the source data (i.e. the requirements) for the chart and how to calculate the requirement status for each one of the requirements.
Source data
Source "requirement" issues can be directly provided using a saved filter or by specificiend some requirement fields:
- Saved filter: A saved filter containing requirement issues
- Fix Version: version assigned to the requirement (you can also choose whether to include the previous versions - equivalent in JQL to fixVersion <= X. The default value for this option can be changed in Xray configuration.)
- Key or Summary: requirement's key or summary
- Assignee: requirement's assignee
- Component: component assigned to requirement
- Workflow Status: workflow status
- Resolution: workflow resoluton
Analysis
In the left side it's possible to define the analysis strategy, i.e. the way you want to analyze the selected/filtered requirements. You can either choose to analyze by Version or Test Plan, and complement it with a Test Environment.
When choosing analysis by Version, then the latest results from Test Executions for the specified version are taken into account. If you choose Test Plan, only Test Executions (and related results) related with the given Test Plan are considered for the calculation of the requirement status.
The (Test) Environment , when specified, considers only executions made for the specified environment.
It is also possible to visually group the requirements, by Priority, Component and other fields, so you can analyze requirements from different perspectives which may be more relevant to you.
Tips
For more info on requirement coverage analysis, please see Requirement Coverage Analysis.
Example
Each bar in the chart represents a group of Requirements with a different value provided by the grouping field. Stacked within each bar are the Requirements grouped by coverage status: OK, NOK, NOT RUN, UNKNOWN and UNCOVERED.
Because this is a normalised chart, the bars are always 100% wide.
The overall coverage Requirement chart is interactive. Hovering the different bars shows a small popup with the information of the specific series (Status, Grouping Field and Percentage). Also, it is possible to deactivate a particular series by clicking in the series legend.
The chart also supports drill-down. When a section is selected, a table appears below the chart with the Requirement issues.
For each Requirement issue, this table shows the following indicators:
- Total Tests
- Passed
- Failed
- Unknown
The table also contains a column with a progress bar that shows the completeness of a Requirement.
