User
scenarios
A feature can technically work and still break someone's journey. That's why I test the complete user story, not just individual buttons.
From start to outcome
I test the whole sequence, including going back, errors, interruptions, and retries.
Beyond the happy path
I consider that users may not know the product's rules, may make mistakes, or may take a path the team never expected.
Create a task through Moti and receive a reminder
Moti is running. Access to Reminders is allowed. The user is in Moti's chat or planner.
- 01Describe
The user asks to create a task and provides a due date and time.
- 02Review
Moti shows the parsed title, date, time, and notification.
- 03Save
The user confirms task creation.
- 04Get a reminder
Moti's own reminder bubble appears on time, without duplicates.
- 05Complete
The user marks the task complete and the status syncs.
- No permission: explain how to grant it and preserve the entered data.
- Missing date or time: ask only for the missing information.
- App restarted: restore the queue without repeating the bubble.
- Matching data in Moti and Apple Reminders.
- Correct timing, including advance notifications.
- Snoozing, completion, and no duplicates.
The task was created and the title synced. The time in Apple Reminders differed by 15 minutes, and Moti's own bubble did not appear when due.
CONCLUSIONCreating a record alone does not complete the user journey. Without a correct due time and reminder delivery, the user's main goal is not achieved.