Mission 02 Mission 02 Start-to-Finish Lab Guide
📥 Lab input
- •
day7_meeting_notes.md(meeting notes)
💾 Lab output
- •
day7_e2e_validation.md
1. Story and lab background
Simulate, in chat with a Codex persona, the unbroken scenario (End-to-End) from a real customer downloading the app and opening it for the first time to finishing a booking, and finally prove a flawless service that flows without breaks.
2. Learning goals
- Build an unbroken user scenario (E2E) from sign-up to list search and back from payment.
- Listen to the comprehension barriers of an older persona who's a bit awkward with digital devices.
- Fix NG (error) points and build a completable scenario check doc (`day7_e2e_validation.md`).
🛠️ Follow-along lab guide
- Create the lab file: press the download button below and save
day7_meeting_notes.mdin theautomation/folder. - Persona role-play: tell Codex Client to play a 'self-employed person in their 50s unfamiliar with smartphones' and have a journey scenario test conversation.
- Write the check report: fix the guard for restoring sign-up info where the persona felt pain, and build an overall check report (`day7_e2e_validation.md`) with an optimized state matrix.
Download lab materials
Codex request prompt
Mission 02 Prompt
You are a self-employed beginner in your 50s who is new to booking and paying in mobile apps. Assuming you use the E2E scenario from sign-up to payment complete, produce a vivid user scenario check (E2E Validation) showing whether my logic has any sections that cause frustration or risk you quitting midway.
4. Example output
Codex analyzes the meeting notes and outputs a normalized data entity mapping and Mermaid ERD script like below.
| File | Persona | Key result | Fix |
|---|---|---|---|
| day7_e2e_validation.md | Self-employed mobile beginner in their 50s | Sign-up email typo check OK, back-button restore NG ➔ fixed to OK | Filter state kept and restored with sessionStorage |
5. AI use points
- E2E mock run: finds break points across the whole chain of scenarios that planners didn't foresee.
- Catch comprehension friction: collects a virtual user's struggle log and suggests friendlier, more usable interface improvements.