manual-test-caseslisted
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# Manual Test Cases
A manual test case is written for a person who has never seen the feature,
executing it under time pressure, who must be able to say "pass" or "fail"
without asking anyone a question. Everything below follows from that.
This skill produces two things: a readable document, and an import file whose
columns match the target TMS. Both come from the same source, so they cannot
disagree.
## Manual cases are a peer of automation, not a by-product
Write these in the design phase, alongside the automated suites — not afterwards
as an export of what was automated. Three reasons this ordering matters:
- A manual tester usually needs cases **before** automation exists, and on many
projects automation never arrives at all
- Cases derived from automated code inherit its shape, and automated tests skip
things a human should check: layout, wording, perceived speed, whether the flow
makes sense
- `manual-test-cases`, `automation-api` and `automation-ui` are three **projections
of the same scenario JSON**. None of them is the source for the others, and
deriving one from another is how they drift
Generate manual cases for everything, then mark which are automated. A case
covered by automation stays in the catalogue with `Automation status: Automated`
— it is still the documentation of what is verified, and it is what somebody
executes when the suite is unavailable or the result is disputed.
## Where the content comes from
In order of preference. Use the hig