TemplateFREE⏱️ 20-40 minutes
Test Case Template for Agile Teams
A structured test case writing template with acceptance criteria, preconditions, expected results, and traceability.
Updated 2026-03-04
Test Case
| # | Item | Category | Priority | Owner | Status | Notes | |
|---|---|---|---|---|---|---|---|
| 1 | |||||||
| 2 | |||||||
| 3 | |||||||
| 4 | |||||||
| 5 |
#1
#2
#3
#4
#5
Edit the values above to try it with your own data. Your changes are saved locally.
Get this template
Choose your preferred format. Google Sheets and Notion are free, no account needed.
Frequently Asked Questions
How many test steps should a test case have?+
Aim for 5-12 steps per test case. Fewer than 5 steps usually means the test is too simple to document or you are skipping important verification points. More than 12 steps suggests you are combining multiple scenarios. Split long test cases into smaller, focused ones. Each test case should verify one specific behavior or user flow.
Should PMs write test cases?+
PMs should write [acceptance criteria](/glossary/acceptance-criteria) on user stories. QA translates those criteria into formal test cases with precise steps and expected results. PMs should review test cases to confirm they match the intended behavior, especially for P0 flows. If a PM reads a test case and does not understand what it validates, the test case needs rewriting.
When should test cases be written relative to development?+
Write test cases after the user story is refined but before development starts. This approach, sometimes called test-first design, forces the team to think through expected behavior and edge cases before writing code. Engineers can reference the test cases during implementation. Update test cases during development if the implementation reveals new scenarios. The [Technical PM Handbook](/technical-pm-guide) discusses how to integrate testing into the development workflow.
How do I decide which test cases to automate?+
Automate test cases that run frequently (every build or every sprint), that are deterministic (same input always produces same output), and that cover stable functionality (not likely to change next sprint). Use the [RICE Calculator](/tools/rice-calculator) to prioritize: Reach = how often the test runs, Impact = severity of a missed bug, Confidence = how reliably the test can be automated, Effort = engineering time to build and maintain.
What is the difference between a test case and a test scenario?+
A test scenario is a high-level description of what to test: "Verify that a user can complete checkout with a credit card." A test case is the detailed, step-by-step specification of exactly how to test it, including preconditions, test data, and expected results for each step. One scenario typically maps to 3-10 test cases covering the happy path, error paths, and edge cases. ---
Related Tools
Explore More Templates
Browse our full library of PM templates, or generate a custom version with AI.