Skip to content

Coverage

2 min read

In most tools, coverage means one thing: executed tests divided by total tests. In Hawzu, coverage is broader. Observatory helps you answer not only whether tests passed, but whether the right things are being tested — across several dimensions.

Coverage is a distinct insight category because these questions come up constantly in audits, release reviews, and quality planning, and most reporting tools ignore them.


Coverage in Observatory spans multiple dimensions:

  • Requirement coverage — how many requirements have at least one linked test.
  • Orphan tests — tests that are not linked to any requirement, and therefore have no traceability.
  • Automation coverage — how much of the suite is automated versus manual.
  • Traceability — how tests and defects map back to requirements.
  • Release coverage — how much of a release’s scope is covered and executed.
  • Execution coverage — how much of the planned suite has actually been run.
  • Suite growth — how the total number of tests changes over time.

Each coverage dimension maps to a ready-made insight:

QuestionInsightWhat it shows
Are all requirements backed by tests?Requirements CoverageRequirements split into those with at least one linked test versus those with none.
How many tests aren’t linked to a requirement?Orphan TestsTest cases split into linked versus orphan (no requirement).
Is our test suite growing?Tests Over TimeThe total number of test cases in the suite, trended over time.
How much requirement coverage does each run hit?Requirements Covered per ExecutionRequirement coverage reached during each execution.
Which requirements carry the most tests?Test Cases per RequirementTest design footprint per requirement.

Automation coverage is covered by the Automation category, and release coverage by the Coverage % measure on Release charts.


Observatory’s coverage insights are the dashboard-level view. For deeper, dedicated coverage analysis, Hawzu also provides standalone reports:

  • The Coverage report breaks coverage down by folder and requirement type, and lists uncovered requirements and stale tests.
  • The Traceability Matrix maps requirements to their linked tests and defects.

Use the insights here for at-a-glance monitoring, and the reports when you need to act on specific gaps.