1.11Step 5 — Discover the UI journeys that actually matter

A good harness does not start by automating random pages. It starts with meaningful journeys.

Identify at least these categories

Smoke journeys

Short, critical checks that prove the application is alive.

Examples:

• sign in
• load dashboard
• browse catalog
• open detail page
• complete checkout
• create a simple record
• fetch a critical account page

Regression journeys

Broader user behavior and business logic.

Examples:

• edit profile
• update payment method
• create/edit/delete flow
• permission checks
• filtering/sorting/search
• validation and error handling

Accessibility targets

Pages worth early a11y coverage.

Examples:

• sign-in form
• checkout flow
• key dashboard
• search results
• important modal/dialog workflows

What to avoid at this stage

Do not over-specify every test case yet.
This chapter is for journey mapping, not full suite design.

Copy-paste prompt for Claude Code

Based on the discovered product structure, identify the most important UI journeys.

Organize them into:
- smoke journeys
- regression journeys
- accessibility targets

Write the result into:
- docs/specs/ui-journeys.md

Focus on business-critical user flows rather than exhaustive test cases.