This page is maintained for older versions of Spira only. The latest documentation can be found at: https://spiradoc.inflectra.com

Spira 4.2 User Manual Help Viewer

1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access
Search:
1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access

3.4.4. Requirements Coverage

This section consists of a bar graph that displays the aggregated count of requirements test coverage for the project. The Passed, Failed, Blocked, Caution and Not-Run bars indicate the total count of requirements that have tests covering them, allocated across the execution status of the covering tests. For example if a requirement is covered by four tests, two that have passed, one that has failed and one that has not yet been run, the counts would be passed = 0.5, failed = 0.25 and not-run 0.25. These fractional quantities are then summed across all the requirements to give the execution status breakdown of the covered requirements.

In addition to the five statuses for the covered requirements, the sixth (“Not Covered”) bar depicts the total number of requirements that have no tests covering them, putting the five other bars into perspective. Typically a project is in good health if the “Not Covered” bar is zero, and the count of “Passed” requirements is greater than “Failed”, “Caution” or “Not Run”. The greatest risk lies with the “Blocked”, “Not Covered” and “Not Run” status codes, since the severity/quantity of any bugs lurking within is not yet fully known.

If you position the mouse pointer over any of the four bars, the color of the bar changes slightly and the underlying raw data is displayed as a tooltip, together with the percentage equivalent. Clicking on the any of the bars in the chart will take you to the requirements list page (see section 4.1) with the corresponding filters set.

When you filter the project home by release/iteration, this widget will filter the requirements coverage graph to only include requirements that are specifically mapped to the selected release/iteration. This is useful when you want to determine the test coverage of new requirements that are being added to the specific release/iteration. If instead you want to determine the regression test coverage for a release, you should add the separate “Requirements Regression Coverage” widget to the page instead.