Page History
Shows a daily historical view of Requirements the Requirement coverage. It is possible to see the evolution of the Requirement's coverage status over time for a particular Analysis Version (or Test Plan) and Test Environment.
| Note | ||
|---|---|---|
| ||
To be able to use this report , your project must have the Requirement Coverage enabled. See how in Configure JIRA project to be used as Requirements projectt. |
...
Aim
This report allows users to evaluate the progress of the requirement coverage status, which implicitly takes into account the testing results associated with each requirement.
...
This report is either accessible from "Xray Reports" icon on the project left sidebar side bar or from the standard "Reports" icon, which includes other kinds 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 specifying specificiend some requirement fields:
- Saved filter: a A saved filter containing requirement issues
- Fix Version: version assigned to the requirement (You 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 the 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
On 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 either by Version or Test Plan, and complement it with a Test Environment.
If you choose 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) associated related with the given Test Plan are considered in for the calculation of the requirement status.
If the The (Test) Environment is , when specified, then considers only the executions that ran in made for the specified environment are considered.
| Info | ||
|---|---|---|
| ||
For more information, please check the info on requirement coverage analysis, please see Requirements Coverage Analysis. |
...
This graphical report is composed of by two similar vertical stacked bar charts: one . One showing absolute values and the other showing relative percentage normalized normalised values. Both charts are interactive. Hovering over the different bars shows a small popup with the information about of the specific series (Status~Grouping, Date and Percentage/Value). You can Also, it is possible to deactivate a particular series by clicking in the series legend.
...