UC002: List All Tasks¶
Overview¶
| Property | Value |
|---|---|
| ID | UC002 |
| Level | User Goal |
| Primary Actor | User |
| Trigger | User opens the home page of the Task Manager web application. |
| Precondition | None. The task list may be empty. |
| Success Guarantee | The User sees all currently stored Task records. |
| Related Rules | — |
| Related Feature | features/UC002-list-tasks.feature |
Goal¶
The User wants to see all their tasks in one place so they can get an overview of outstanding work. The system returns all tasks without filtering or pagination. This use case does not modify any data.
Main Success Scenario¶
- User navigates to the home page.
- System fetches all
Taskrecords from the database. - System responds with HTTP 200 and the list of tasks (may be empty).
- System renders the task list in the UI.
Extensions (Alternate Flows)¶
2a. No tasks exist yet:
- System returns HTTP 200 with an empty array
[]. - UI displays an empty-state message (e.g., "No tasks yet. Create your first task.").
- Use case ends successfully.
Transaction Boundary¶
Read-only. No transaction required; a single database read query suffices.
Sequence Diagram¶
BDD Scenarios¶
The feature file is the single source of truth for behaviour — it is also executed as an acceptance test. See features/UC002-list-tasks.feature.