Written from your specs AI Test Case Generator Map the coverage, then write the cases you pick Do the test once Record a Test Beta Get readable steps and Playwright + pytest scripts It can only read MCP server Let Claude, ChatGPT or Cursor read your test data Compare Test Management OracleAI Pricing Blog Docs Login Start free
Atlas

You changed the payment service. Now, what has to be retested?

Hawzu maps out your app, then tells you what to rerun after a change and why each test is on the list.

Built from Test foldersCanon documentsLinked requirementsYour own edits
Answers What to retestJourney healthCoverage gapsA shareable map
What to retest

A retest list you can hand to someone

Pick the part that changed. Atlas sorts the tests that depend on it by how urgent they are.

How it works

Hawzu drafts the map. You review it.

It starts from your test folders and the specs you share.

  1. Sync

    One click turns your test folders into a first map.

  2. Let it suggest the rest

    Hawzu reads your documents in Canon and suggests the areas and screens your folders missed. You approve each one.

  3. Tidy up

    Rename things, link requirements and mark what depends on what. Flag the journeys a release can't ship without.

What goes on the map
  • Area A top-level part of the product
  • Module A grouping inside an area
  • Feature Something a user can do
  • Screen A page or view they do it on
  • Behaviour One observable action or rule
  • Integration Another system this connects to
  • State A condition the product can be in
  • Note Context that is not part of the structure
Why it stays useful

A map that doesn't go stale next week

Journeys judged by their weakest step

If checkout has no test, the whole purchase journey is flagged, even when every other step passes.

Re-syncing keeps your edits

Rename or move things, then sync again. Your changes stay, and anything you deleted stays deleted.

Everyone sees the same map

Everyone in the project can read it. Only some roles can change it.

Coverage on the map

See which parts of your app have no tests

Every item on the map is coloured by how its tests are doing.

Good to know

Three promises

Nothing the AI suggests is added without you

Suggestions arrive as a draft, and you pick the ones to keep.

Clear buckets, not a mystery score

You get Must retest, Should retest or Consider. There's no percentage to take on faith.

It doesn't read your code

Atlas works from your tests, specs and edits. What your team never wrote down shows up as a gap.

Monday · 9:15 AM

“It's a small change to auth.”

Someone picks the auth item in Atlas and gets twenty-eight test cases back, seven of them must retest. The estimate changes in the meeting instead of the Thursday before release.

Hawzu learns your specs too

It also learns from the specs you share in Canon. Test cases written from a map item follow them.

Canon — AI that shows its sources

Find out what your next change touches.

Every feature on every plan. Free for five people, then $20 per member. No credit card.

Talk to Us

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

Book a demo

Pick a time that works — we'll confirm by email and send a calendar invite.

Select a date

Available times

Times shown in your timezone: —