Write test cases from acceptance criteria

A story is ready for QA and the criteria need turning into concrete checks.

Turn these acceptance criteria into test cases.

For each case give: an ID, preconditions, steps, expected result, and which criterion it covers.

Rules:
1. One case per assertion. Do not bundle five checks into one long script.
2. Expected results must be observable, with the specific text, state or value expected. Not "the page works".
3. Cover the negative path for every criterion: rejected input, missing permission, dependency down.
4. Flag any criterion that cannot be tested as written, and say what it would need to become testable.
5. List the cases that should be automated and the ones that are only worth doing manually, with a reason.

End with the gaps: behaviour that clearly matters but appears in no criterion.

Acceptance criteria:

Finding coverage gaps. Working out which behaviours, edge cases and error paths nothing currently checks.