Intermediate

Test Every User Path

Systematically walk every path a user can take and verify each works - the complete functional test pass.

5 steps15 verify checks60-120 minutesWorks with: emergent · chatgpt · claude · cursor

Start Guided Walkthrough

#testing #user-paths #qa #verification #coverage

The Route

0/5 verified

Map every user path

You test what you have mapped - build the complete path inventory.

3 checks 02

Execute the happy paths

Prove the core promises work end to end first.

3 checks 03

Execute alternate and error paths

Real users cancel, go back, and type garbage - test that world.

3 checks 04

Fix all failures

Convert the FAIL list to fixes, worst-first.

3 checks 05

Final regression sweep

Fixes break things - run the full map once more.

3 checks

Every step ends at a Verify Gate. Do not continue until every check passes.

Context Pack

Paste this first. It briefs the AI on requirements, constraints, and the Definition of Done before your first build prompt.

Context Pack

PROJECT CONTEXT:
I want to verify my entire app works by testing every path a real user could take, not just the happy path.

GOAL:
Map all user paths, execute each with variations, and fix everything that fails.

REQUIREMENTS:
- A complete user-path map (happy, alternate, error paths)
- Executed tests with recorded results per path
- Edge and error variations per path
- All discovered failures fixed and re-tested

CONSTRAINTS:
- Observed behavior only - no assumed passes
- Error paths are mandatory, not optional

DEFINITION OF DONE:
- Every mapped path has an executed PASS with evidence
- Error variations behave gracefully
- No path dead-ends or silently fails
- Fixes are re-tested, not assumed

COMMON FAILURES TO AVOID:
- Testing only the happy path
- Skipping logged-out/fresh-account perspectives
- Marking paths passed from code reading
- Fixing bugs without re-running the failed path

Paste this into your AI builder first. It teaches the AI what you want before you give it the build prompt.

Related routes

More QA flows that share ground with this one.

Evidence Checklist

Prove your app works with evidence: build a claim-by-claim verification pack with receipts.

01Inventory every claim

02Define verification procedures

03Execute and collect evidence

+2 more steps to Done

Best foryour first pass at this - no prior setup assumed

5 steps45-60 minutesBeginner

Start Route Details

Auth Flow QA

Dedicated auth testing: signup, login, sessions, guards, reset, and the edge cases that expose fake auth.

01Test the signup surface

02Test the login surface

03Test the session lifecycle

+2 more steps to Done

Best forbuilders who have shipped a basic app before

5 steps45-75 minutesIntermediate

Start Route Details

Mobile QA Checklist

A rigorous mobile QA pass: layouts, touch, keyboards, and the full core journey on phone-sized screens.

01Layout pass at phone widths

02Fix layout breaks

03Touch and gesture pass

+2 more steps to Done

Best foryour first pass at this - no prior setup assumed

5 steps45-60 minutesBeginner

Start Route Details