Cases
Problems you can catch before your users do
Each case starts with something that goes wrong in real products, shows why ordinary tests miss it, and sets it up in Journey Lanes step by step. They use the same sample portal as the example on the home page.
- New customers can’t finish onboarding after a deploy A super admin creates a company and its admin, an invitation goes out, and the new admin signs in. One deploy breaks a link in that chain. A deploy check runs the onboarding flow after every deploy
- A company admin can open another company’s orders Change the id in the address and the API returns someone else’s order. Every screen looks right. The access audit probes every role with ids that aren’t theirs
- Ordering slows to a crawl when everyone orders at once Fine for one employee. Too slow when a whole company orders at the start of the month. A load test on the order step, with limits for p95 and errors
- Nobody can log in after the login page got a new look A theme update on the identity provider changes the form. The API tests stay green while real people are locked out. A monitored flow that signs in through the real login page
- A role change quietly gives employees admin rights One line in the role hierarchy, and employees can open the invoices. No screen shows it. A tour for the role, with checks that what it may not do is refused
- The frontend team waits for an API that isn’t deployed yet The endpoints exist in a branch, but there’s no server to call, and the hand-written mock is already out of date. A mock backend built from the branch’s code
- An order fails somewhere across three services Orders, products and invoices are separate services. When the journey breaks, everyone looks at their own logs. One flow across the services, each step sent to the service that defines it
Start with the case that worries you most
Most teams begin with one journey their customers can’t do without, and add the rest as they go.