User Journey Testing
Purpose
Validate work through a realistic user path.
When to Use
Use for UX, tool workflows, onboarding, and generated instructions.
Inputs
User goal, steps, expected result, viewport/tool/runtime context.
Steps
- State the user's goal.
- Walk the end-to-end steps.
- Record friction, failure, or confusion.
- Update instructions or mark blockers.
Gates
The journey either succeeds or has a clear blocker and next action.
Evidence
Journey notes, screenshots when safe, command output, or report.
Anti-Patterns
Testing only implementation internals and ignoring the user outcome.
Related
e2e-test-matrix, output-readability-gate