PhraseryPhrasery homeGet Phrasery
Tests & QA21 categories

Write a manual QA script someone else can run

Handing regression testing to a person who did not build the feature.

Longmanualqadocumentation
Write a manual QA script for the feature below, for someone unfamiliar with it.

Rules:
1. Start with setup: the account, role, data and environment needed, stated so the tester can confirm they have it before starting.
2. Numbered steps, one action each. Never "fill in the form", instead say which fields and what values.
3. Expected result after each step, specific enough that a tester with no product knowledge can judge pass or fail.
4. Mark the steps where a subtle problem is most likely, and say what to look closely at.
5. Include how to reset between runs.
6. End with a short list of things to note but not fail on, such as cosmetic issues.

Keep the whole script under 30 steps. If it cannot be, split it into separate scripts.

Feature:

Making it yours

  • Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
  • Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
  • If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.

Beyond unit tests. Manual QA, exploratory charters, accessibility, load, and contracts between services.

Related prompts

Keep this one

Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.

Add to your browser โ€” free