User Journeys Skill For defining and testing real user experiences not just specs, but actual flows humans take through your application. Philosophy Specs test features. Journeys test experiences. A feature can pass all specs but still deliver a terrible experience. User journeys capture: How users actually navigate (not how we think they should) Emotional states at each step (frustrated, confused, delighted) Recovery from mistakes (users will make them) Real world conditions (slow networks, interruptions, distractions) Journey Documentation Structure Journey Template Critical Journey Examples Signup to First Value Checkout Purchase Journey Testing with Playwright Journey Test Structure Error Recovery Tests User Experience Validation UX Checklist per Journey Step Automated UX Checks Journey Metrics Dashboard Track journey health with these metrics: Common Journey Patterns Progressive Disclosure Journey User sees simple view first, complexity revealed as needed. Guided Setup Journey Hand hold new users through initial configuration. Recovery Journey User returns after failure or abandonment. Anti Patterns Happy path only Test error recovery, not just success Spec driven testing Test user goals, not features Ignoring time Measure how long journeys take Desktop only Test mobile journeys separately Skipping emotions Consider user frustration points No metrics Track journey completion and drop off Static journeys Update as user behavior evolves Quick Reference Journey Priorities Priority Criteria Test Frequency Critical Revenue, core value Every deploy High Daily user actions Daily Medium Weekly features Weekly Low Edge cases On change Package.json Scripts Journey Documentation Checklist [ ] User goal clearly stated [ ] All steps documented [ ] Success criteria per step [ ] Error scenarios covered [ ] Recovery paths defined [ ] Metrics identified [ ] E2E test linked

user-journeys