The coverage map
One line per scenario, with its lens and the requirement it tests.
You see up to forty scenarios and what's missing first, then pick the ones worth writing.
The coverage map on real requirements. R5 has nothing proposed.
You check the list of scenarios first. Steps are written only for the ones you tick.
One line per scenario, with its lens and the requirement it tests.
Full steps for the scenarios you ticked.
Stage two. A full case with an expected result on every step.
A case written from an attached document isn't linked to any requirement.
When your source is thin, you get fewer scenarios and a note saying why.
It checks the test cases you already have and proposes what's missing.
Specs say what should happen. They rarely say what happens when two people do it at once.
It won't make up details that aren't in what you gave it.
Requirements with nothing proposed are named on screen.
If a source is too long, you're told how much of it was used.
Cases follow the specs you've shared with Hawzu. You can switch it off per run.
It won't create requirements, suites or releases. It saves nothing you haven't ticked.
The Refunds v2 spec lands as a PDF. You drop it in, tick six requirements and press Generate.
The real finding was REQ-118. Nobody had written down what happens to a partial refund on a cancelled order.
Once you add them, they work like any case you wrote by hand. A small AI tag shows where they came from.
Open the Repository and choose Draft test cases with Oracle. Pick up to ten requirements, paste a spec or attach up to three documents. Hawzu maps up to forty scenarios first. Tick the ones worth testing and it writes full test cases. Nothing is saved until you accept them.
Yes. Attach Word, Markdown or text files, or one PDF up to 8 MB, or paste the text. If your project has Canon documents, the generator reads those too by default, and every draft shows which document and section it came from.
It checks the test cases already linked to your requirements and skips scenarios they cover, so the map shows what's missing instead of repeating what you have.
Start from specific requirements — rules, limits and error cases, not just feature names. Review the scenario map before anything is written, because that's where gaps show. Then check each draft against its source tag before you accept it.
It's on every plan, including the free plan for five people, within a monthly AI allowance. One credit covers about twelve written test cases. See pricing.
Every AI feature on every plan. Free for five people, $20 per member after — no credit card.