Task 02 Task 02 User scenario verification practice guide
📥 Practice Input
- •
day7_meeting_notes.md(meeting minutes)
💾 Practice output (Output)
- •
day7_scenario_solution.js
1. Story and practice background
The development team has announced that they have perfected the reservation details creation feature. However, one beta tester selected a detailed reservation to make a reservation, and then clicked 'back' to check the rating of the expert before confirming the reservation. Then, all the reservation slot date information that had just been entered was reset to blank, and the user became angry and closed the app.
From the developer's perspective, he thought that individual functions that saved reservation data in the database worked well, but when actual users use the app to go through a long scenario (User Journey Flow) from signing up to expert search, time reservation, and payment, information omissions and learning flow disruptions often occur. In this exercise, we will use Codex AI to track all functional flows from the beginning and end of a scenario in one breath, and how to find and correct disconnected sections in the flow.
2. Learning objectives
- Beyond fragmentary functional unit tests, you can look at the user’s journey (Scenario Flow) three-dimensionally.
- The flow can be diagnosed to see how previous state values are maintained and lost within a continuous function call structure.
- Using AI guides, you can formalize essential checklists that are easy to miss when checking scenarios.
🛠️Practical guide to follow along
- Create file for practice: Click the download button below
day7_meeting_notes.mdfileautomation/Save it within the folder. - Codex scenario analysis instructions: Enter the **Codex request prompt** below in the Codex Client prompt input box and send.
- Writing session retention scripts: Attach the sessionStorage-based search restoration script output as feedback to the actual logic and verify that the filter category is safely reinstalled when going back.
Download practice materials
Codex request prompt
Task 02 Prompt
By analyzing the step-by-step call sequence of the provided day7_user_flow.md specification (Sign up ➔ Expert search ➔ Detailed reservation ➔ Virtual payment), diagnose the two core sections where information loss is most likely to occur when a user takes this route, and suggest a state preservation logic structure as an alternative code to prevent this.
4. Example results
Codex analyzes the meeting transcript and outputs normalized data entity mappings and a Mermaid ERD script as shown below.
| file name | state caching | Backup destination information | Resilience Guarantee Section |
|---|---|---|---|
| day7_scenario_solution.js | Utilizing sessionStorage | Search filter values (Category, Rating, etc.) | Preserve filter when regressing list |
5. AI utilization points
- Identify scenario gaps: Identify data movement bottlenecks and restoration factors between multi-screen specifications that go unnoticed in single-source reports.
- User Experience Threat Mapping: AI points out the 'procedures that make users tired' hidden behind 'developmentally perfect logic' from a third party's perspective.