MarkThatDownTemplates
Record scope, setup, cases, expected outcomes, and evidence. Use the template to show what was actually tested.
# Test plan
Target. [Feature and version]
## Scope
[Behavior to verify]
## Setup
- [Environment and fixtures]
## Cases
| Case | Input or action | Expected result | Evidence |
| --- | --- | --- | --- |
| [Normal case] | [Action] | [Result] | [Record] |
| [Boundary] | [Action] | [Result] | [Record] |
| [Failure] | [Action] | [Recovery] | [Record] |
## Untested
- [Gap and reason]
## Exit decision
[Pass, fail, or pending and why]
An ordinary Markdown file. No signup required.
Cover a normal path, a meaningful boundary, and an expected failure. A test that repeats implementation details may miss the user’s actual result.
Record the target version and actual observation. Mark an unavailable check as untested rather than passed.
Reviewed October 2, 2026. Maintained by Humenhuk.
Original practical template. Adapt the examples to your own work.