TICKET — report title

One line: what the work had to prove.
Branch branch-name · Book Name (env) · DD Month YYYY · driven with tool

Result summary

# Check Result
1 What was checked Pass
2 What was checked Fail
3 What was not checked Not testable

One line that groups the checks: which are the change, which are defects the test found, which were blocked.

How the test was built

Starting state, why the obvious data was no use, and the case that was built instead.

Step What
1 Action taken.

Check 1 — short claim Pass

Plain description of the screenshot
Label. What the reader must see in this shot, and why it matters.

Why this proves it. Tie the evidence back to the code that changed.

Check 2 — short claim Fail

{"paste":"the request or the error, escaped"}
Description
Label. Caption.
Description
Label. Caption.

Other findings

F1 — short title Info

What was found, and what it blocks or costs.

Supporting detail that is not the finding itself.

Not covered

Check Why
3. Name of the check Reason, and how much risk it leaves.

Test data left behind

Item State Action
What was created Current state Delete it. How.

Related files

A copy of each one travels inside this report, so the links keep working wherever it is moved.

File What it is
test-plan.md The steps, written before the work started