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.
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 seven decision-ready reports — each one scored, scoped to a release or run, and built to sign off.
Release Readiness — one release, scored 0–100, with every risk behind the number.
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.
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.
What is CI running that we can't see?
Automation Health
The tests your pipelines run that map to no test case — and the ones quietly getting slower, ranked by the gap between their average and their worst run.
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.
See the report, not a mockup
Real screens from inside Hawzu. Click through each one.
One number the whole room agrees on
Release Readiness turns four parts of the release into a single 0–100 score — the same rules every time, so the number is a fact, not an opinion. No black box: the report shows how each part scored.
Not ready
At risk
Ready
Test Execution how much has run Quality how much passed Defect Health open blockers, old or overdue defects Requirements fully verified
Monday · 9:04 AM
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.
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 on every plan. Free for five people, $20 per member after — no credit card.