1Business context
TaskBoard is an agile project-management tool. Teams create issues, organise them on a Kanban board, track sub-tasks and manage sprints with a burndown chart.
A sprint Kanban you can drag across (or use the move menu), a create-issue modal with label chips, issue pages with sub-task progress and comments, an SVG burndown chart, and a backlog with bulk move to sprint.
2Users & roles
- 👤 Team member — creates issues, moves cards, manages the backlog and sprint
3Modules & screens
| Screen | Route | What it does |
|---|---|---|
| Board | /apps/projects | Kanban columns, assignee filters, drag and drop, create issue |
| Issue detail | /apps/projects/task/[key] | Sub-tasks with progress |
| Backlog | /apps/projects/backlog | Select issues and move them into the sprint |
| Sprint report | /apps/projects/sprint | SVG burndown chart with data points |
4Main end-to-end journey
Issue from creation to done
- Create story "Add login rate limiting" (high, amir, 5 points, label security)
- Open PA-9 and add 2 sub-tasks, tick one
- Move it to Done
- Open Sprint
- Pull PA-6 from the backlog into the sprint
Expected: PA-9 created and in Done; sub-task progress 1/2; burndown 26 pts total with 18 remaining; backlog shows 2 issues
5Business rules & validations
- Assignee avatars filterBeginner
filter-assignee-* toggles (aria-pressed) and only-mine narrow the board; assert board-count.
- Create-issue validationIntermediate
save-task with blanks shows task-errors and error-*; a short title is rejected.
- Chips with EnterIntermediate
Type in label-input and press Enter (or add-label); remove with remove-label-*.
- Drag across columnsAdvanced
Drag a task-card onto col-review (HTML5 DnD); or use move-task-<key>. col-count-* updates.
- Sub-task progressBeginner
Add sub-tasks, tick subtask-0 and assert subtask-progress “1/2”.
- SVG chart dataAdvanced
burndown-point circles carry data-day/data-points; the last point equals burndown-remaining.
- Bulk moveIntermediate
Tick select-<key> in the backlog and move-to-sprint; the issues appear on the board.
6Test data & credentials
- URL
- /apps/projects
- Sprint
- Sprint 14 · day 6 of 10
- Issue keys
- PA-1 … (next PA-9)
- Login
- not required
7Glossary
- Issue key
- PA-1, PA-2 … — the next new issue is PA-9
- Story points
- Effort estimate summed in the burndown
- Burndown
- Chart of remaining points per sprint day
8Watch-outs for automation
- ⚠️Drag and drop is HTML5 — use the Move menu for Selenium/Cypress
- ⚠️Labels are added with Enter
- ⚠️Burndown points expose data-day / data-points attributes
9Suggested test strategy
1 · Smoke
2
P1 positive and end-to-end cases — run on every build.
2 · Regression
13
All cases, incl. 2 negative and 2 edge — run before release.
3 · End-to-end
3
Full user journeys — run nightly.
Start with these smoke cases
- TASKBOARD-01 — Create an issue
- TASKBOARD-E2E-01 — Issue from creation to done