A structured step editor, reusable shared steps, parameters and datasets, dynamic and hybrid suites, and a folder-tree repository built for thousands of cases — with executions that stay in sync and import from the tool you're leaving.
Author cases that don't rot, organize thousands without friction, and run them with the discipline a release deserves — all in one place.
Write test cases as structured step + expected-result rows — each one rich text, with inline images and attachments, dragged into any order. Set preconditions once, and switch a case to a single freeform step or Gherkin/BDD when that fits the work better.
Define a login or setup sequence a single time as a shared step, then reference it from any case across the project or the whole workspace. Edit it in one place and every case that uses it updates — and you can see exactly which cases those are.
Drop a parameter straight into step text, attach a dataset, and the case runs once per row with real values swapped in at execution time. Try to delete a parameter that's in use and Hawzu shows you every case and shared step it would touch before you do.
Build a suite by hand, by filter, or both. A dynamic suite is a saved query — “all high-priority checkout cases” — that re-populates itself as the repository changes, so a suite is never quietly out of date. Hand-picked cases and live filters sit in the same suite.
Pull cases into a standalone test run or a release execution, distribute them across testers, and record per-step and final results — Passed, Failed, Blocked, Skipped — with evidence, notes, and time spent. Update status in bulk, and when a pulled-in case changes, Hawzu flags the drift and lets you re-sync.
Organize everything in a nested folder tree with custom fields and labels, search and filter across it, bulk-edit or move in place, and restore anything from the recycle bin. Every case carries version numbers and a field-level change history you can scroll back through.
Real screens from inside Hawzu. Click through.
Login just moved to a new SSO screen. You fix the sequence once — in a single shared step — and the forty cases that reference it update at once. The execution already running flags the ones that drifted, and you re-sync them in a click.
Your test cases stay alive — because you maintain them once.
Import from those tools or a plain Excel/CSV — Hawzu maps priorities and types and rebuilds your folder hierarchy as it goes. Pipe automated results in from CI with JUnit/xUnit and the public REST API. Your history comes with you.
The test case is the source of truth the rest of QA draws on — what you run, what fails into a defect, what a release is judged on, and what a requirement is proven by.
Every feature is free while Hawzu is in early access — no credit card required.