Journeys
3 min read
Build journeys to track the end-to-end tasks your users do — sign-up, checkout, password reset — and see at a glance whether each one is covered and passing.
A journey is an end-to-end task a user does, saved as an ordered list of items on the map: a new customer signs up, creates a project and adds their first test case. Each step is one node — one item on the map, such as a screen or a feature.
Build a Journey
Section titled “Build a Journey”-
Select Journeys in the Navigate group of the action rail (the column of buttons on the right edge of the Atlas page).
-
Select Build a journey.
-
Click items in the Tree or Map view, in the order a user goes through them. You need at least two. Remove a wrong step with the × next to it.
-
Enter a name in Name this journey — name it after what the user is trying to do (see What to name a journey).
-
Optionally fill in Persona — new customer, admin, API client. It’s free text and helps the AI test case generator.
-
Pick the criticality (Important by default).
-
Select Save N steps.
To change a journey later, open the ⋮ menu on its card: Rename, change Criticality, Generate test cases… or Delete journey. You can also drag steps to reorder them or remove them.
Click a journey card to follow it on the map: its steps are highlighted and everything else is dimmed. Select Stop following (the × in the bar above the map) to go back.
Criticality
Section titled “Criticality”| Level | Use for |
|---|---|
| Critical | A break means the app is unusable — sign-up, checkout, login |
| Important | Matters, but there’s a workaround |
| Routine | Everything else worth tracking |
Criticality matters in impact analysis: any test on a Critical journey that a change reaches goes straight into Must retest. It also decides the order when you sort journeys by Risk.
Journey Health Is Its Weakest Step
Section titled “Journey Health Is Its Weakest Step”A journey’s health is the health of its worst step, not an average.
The top of the Journeys panel shows how many journeys you have, how many Need attention, and how many have Broken steps.
A broken step is a step whose item has been deleted from the map. The journey keeps the gap so you can see what happened — fix it by removing or replacing the step.
What to Name a Journey
Section titled “What to Name a Journey”Name a journey after what the user is trying to get done, not after the screens it passes through. Checkout is a feature; A returning customer buys with a saved card is a journey — it has a start, an end, and something that can break in the middle.
Good journeys are the paths whose failure would make you stop a release:
- Sign-up to first successful action
- Checkout from start to finish, including failure paths
- Password reset
- Any path that crosses into another system
A journey that covers only one screen or feature is usually better as an item on the map.
Let Atlas Suggest Journeys
Section titled “Let Atlas Suggest Journeys”Atlas can read your test case steps and suggest journeys for you. See Suggest journeys from your test steps.
Generate Test Cases for a Journey
Section titled “Generate Test Cases for a Journey”You can hand a journey to the AI test case generator to write end-to-end test cases. See Generate test cases from Atlas.