Journeys judged by their weakest step
If checkout has no test, the whole purchase journey is flagged, even when every other step passes.
Hawzu maps out your app, then tells you what to rerun after a change and why each test is on the list.
Pick the part that changed. Atlas sorts the tests that depend on it by how urgent they are.
It starts from your test folders and the specs you share.
One click turns your test folders into a first map.
Hawzu reads your documents in Canon and suggests the areas and screens your folders missed. You approve each one.
Rename things, link requirements and mark what depends on what. Flag the journeys a release can't ship without.
If checkout has no test, the whole purchase journey is flagged, even when every other step passes.
Rename or move things, then sync again. Your changes stay, and anything you deleted stays deleted.
Everyone in the project can read it. Only some roles can change it.
Every item on the map is coloured by how its tests are doing.
Suggestions arrive as a draft, and you pick the ones to keep.
You get Must retest, Should retest or Consider. There's no percentage to take on faith.
Atlas works from your tests, specs and edits. What your team never wrote down shows up as a gap.
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.
It also learns from the specs you share in Canon. Test cases written from a map item follow them.
Canon — AI that shows its sourcesEvery feature on every plan. Free for five people, then $20 per member. No credit card.