Most test tools treat a release as a label you tag runs with. In Hawzu the release is the unit of work: requirements, tests, executions, and defects roll up to it, its status gates who can still touch it, and it all lands on one go/no-go you can defend — then freeze the moment you sign off.
Requirements, tests, executions, and defects converge on the release — which becomes a readiness call, then a sign-off you can hand off.
Not a milestone field bolted onto test runs — the living workspace a QA lead plans, gates, analyzes, and signs off a release in.
Requirements, test cases, executions, and defects all roll up to the release you're shipping — with executions gated by its status, and every release comparable to the last. Not a label you tag runs with; the thing you plan, run, and sign off.
Five states — Not Started, In Progress, Paused, Completed, Archived. Pause, complete, or archive a release and its executions freeze: no quiet edits to a result after the fact. The numbers you reported stay the numbers you reported.
Release Analysis rolls every signal into a deterministic GO / AT-RISK / NO-GO verdict and a 0–100 readiness dashboard across test execution, quality, defect health, and requirements — with pulse rings, execution health, and a burndown alongside. The same rules every time, so the score is a fact, not a forecast.
Two ways to run tests: executions anchored to a release that move its readiness, and standalone test runs that don't touch it. Same result model, pace and burndown, and a full activity trail — so a quick smoke run never corrupts your release numbers.
Complete or archive a release and its defect analytics freeze to a stamped “as of” — while in-execution test cases flag any drift from the repository for opt-in refresh. Export a Release or Execution sign-off PDF when you're ready to hand it over.
The workspace's Defects and Requirements tabs put it in one place — defect aging, owners, reopen rate, and unlinked failures on one side; requirement coverage and readiness on the other. No jumping tools to answer “are we actually done?”
Real screens from inside Hawzu. Click through.
They reopen last month's release to tweak a failed test. Hawzu stops them:
The number you signed off on still means what it meant.
This is the workspace they all live in. The readiness report you export, the AI narrative that summarizes it, and the health charts that trend it each get their own deep dive.
Every feature is free while Hawzu is in early access — no credit card required.