Explore Requirements Hierarchy, tasks & automatic coverage roll-up Releases Release-gated executions & go/no-go sign-off Observatory Question-first analytics & dashboards Reports Readiness, coverage & flaky reports Defects Native defect tracking, no Jira AI AI summaries & semantic search Compare Hawzu vs TestRail, Zephyr & more Test Management Pricing Blog Docs Login Start free
Reports

Reports that make the call — not another data export.

Every other tool hands you a spreadsheet and wishes you luck. Hawzu turns your requirements, tests, executions, and defects into six decision-ready reports — each one scored, scoped to a release or run, and built to sign off.

Hawzu's Release Readiness report — a 0–100 go/no-go score with the risks behind it

Release Readiness — one release, scored 0–100, with every risk behind the number.

Six questions

Every report settles one question

Not here's your data. Each report opens on the exact question someone is about to ask you — and settles it.

Are we ready to ship?

Release Readiness

A single 0–100 go/no-go score for one release — with the failing tests, open criticals, and coverage gaps that made it that number.

What's covered — and what caught the bugs?

Requirement Traceability Matrix

Every requirement mapped to the tests that cover it and the defects they caught, with a High / Watch / Healthy risk read on every row.

How did this run actually go?

Test Execution Summary

Pass, fail, blocked, and not-run across every test run and release execution — plus the folders quietly dragging the pass rate down.

What's still untested?

Test Coverage

How much of your requirements have a test and how much of your suite is automated — per folder and requirement type, with the uncovered requirements listed by name.

Which failures can't be trusted?

Flaky Tests

The tests that flip pass-to-fail across runs, classified Stable / Unstable / Flaky — a triage shortlist that separates real breakages from noise.

Who did what this sprint?

Authoring & Execution Activity

Who's writing, running, and filing — throughput and capacity per person, with new contributors surfaced and quiet ones flagged.

A closer look

See the report, not a mockup

Real screens from inside Hawzu. Click through all six.

Release Readiness report — Are we ready to ship?
The 0–100 readiness score, its four weighted inputs, the defect-severity spread, and the failing tests behind the number.
Requirement Traceability Matrix report — What's covered — and what caught the bugs?
Each requirement expanded to its linked test cases and the defects they caught — with a risk read on every row.
Test Execution Summary report — How did this run actually go?
Pass rate and the passed / failed / blocked split, over a per-execution table sorted by what needs attention first.
Test Coverage report — What's still untested?
Requirement coverage and automation share, broken down by requirement type and per folder — untested gaps in plain sight.
Flaky Tests report — Which failures can't be trusted?
Tests ranked by how often they flip, with recent-run streaks, fail rate, and a Flaky / Unstable / Stable call on each.
Authoring & Execution Activity report — Who did what this sprint?
Throughput over time and a per-person split of authored, executed, and filed — new and quiet contributors surfaced.
The score

One number the whole room agrees on

Release Readiness rolls four signals into a single 0–100 score — the same weights every time, so the number is a fact, not an opinion. No black box: the export spells out the formula.

Not ready
At risk
Ready
Pass rate 35% Executed 25% Requirement coverage 20% Open criticals 20%
Monday · 9:04 AM Release review just started

The VP asks the only question that matters — can we ship? You don't share your screen and scroll. You'd already sent one PDF:

  • Release Readiness 78 · Ready
  • Executed · passing 94% · 91%
  • Requirements uncovered 3
  • Open critical defects 1 · owner assigned

The decision arrived before the meeting did.

Built to hand off

A report you can actually send

Scope to exactly one thing

Measure against a whole release (all its executions), a single execution, or a standalone test run. Release Readiness always locks to one release, so the score means one thing.

Filter to the window that matters

Per-report date ranges — Today, 7 / 30 / 90 days, or a custom window — plus search and filters on folder, type, status, and labels.

Export the way you sign off

Pick exactly which sections go in the PDF — and Hawzu remembers next time. Or drop the whole thing into Excel.

When a report isn't enough

Reports are the snapshot you send. When you need the living view, there's a scored Project Health Scorecard, a Release & Execution Analysis workspace with an AI-written readiness narrative, and Observatory dashboards you build yourself.

Run your first report free

Every report is free while Hawzu is in early access — no credit card required.

Talk to Us

Tell us about your QA setup. We'll get back to you within 24 hours.