PhraseryPhrasery homeGet Phrasery
Tests & QA21 categories

Convert a manual test to an automated one

A manual check that has been run by hand thirty times.

Longautomationmanualconversion
Convert the manual test below into an automated one.

1. Identify what the manual test is really verifying, as distinct from the steps it happens to use. Automate the intent, not the clicks.
2. Choose the level to automate at: unit, API, or UI. Prefer the lowest level that still verifies the intent, and justify the choice.
3. Write the test in my framework, with the setup and teardown.
4. Name the parts that should not be automated because they rely on human judgement, such as visual quality or whether wording reads well.
5. Identify what will make this test flaky if written naively: waits, ordering, shared data, animation. Show how to avoid each.
6. Say whether automating this is worth it at all, given how often it runs and how often the feature changes.

Manual test:

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