# Failure and boundary case worksheet

Choose cases for a reason. Case counts do not measure completeness. The fields below are blank planning prompts, not evidence of a tested product.

## Identify the rule

- User task:
- Proposed rule or limit:
- Requirement source or reason:
- Assumptions:
- Behavior that changes across this boundary:

## Candidate cases

For each row, record the condition, the reason it matters and the expected observation. Add or remove categories to fit the real task.

- Expected path:
- Empty or missing input:
- Last permitted value or state:
- First refused value or state:
- Repeated action:
- Interrupted action:
- Changed permission or dependency:
- A combined condition worth checking, and why:

## Expand one case

- Case title:
- Starting context:
- Action or event:
- Observable outcome:
- Information or work that must be preserved:
- Conditions deliberately excluded:
- Expected-result questions still open:

## Evidence and decision

- Status: planned / observed / unresolved
- If observed: date, environment, version, evidence and actual result:
- Uncovered risks:
- Decision: proceed within scope / hold / revise
- Reason:
- Next review trigger:

Do not mark an unrun case as passed. A later automation step needs real assertions and a configured test runner.

---

Well Made Ideas · September 8, 2026

Read the guides: https://wellmadeideas.com/guides

Tool: https://wellmadeideas.com/tools/criteria-builder

Terms: https://wellmadeideas.com/terms

Privacy: https://wellmadeideas.com/privacy

You may adapt and share this original worksheet for personal or commercial use under the Terms. Filled-in copies remain in files you control.