Example: Testing workflow checklist
When to use this
Use this checklist when a team wants visible test sign-off on a story, bug fix, or release item without relying only on comments or external spreadsheets.
What this checklist helps prevent
- Work being shipped before required validation is complete.
- Ambiguity about whether testing is blocked, pending, or finished.
- QA feedback getting lost between multiple work items.
Example checklist
- Test scope is agreed.
- Test data or environment is ready.
- Acceptance criteria were validated.
- Regression checks were completed where relevant.
- Defects found during testing were logged or linked.
- Retesting was completed after fixes.
- Final sign-off or release recommendation is recorded.
Why these items matter
Testing is often a multi-step workflow, not a single action. This checklist makes that workflow visible on the work item itself so both engineering and QA can see what remains.
Common variations
- For lightweight teams, merge scope and environment preparation into one item.
- For bug fixes, add a step for reproducing the original issue first.
- For larger teams, create separate templates for exploratory testing and release validation.
Optional advanced setup
Map Progress to make QA status visible in board cards or queries. This is useful when testing is the main reason work cannot move forward yet.