Turn Manual Test Steps into an Automated Test
Added 2026-10-31
Given manual steps, identify what can be automated and what must stay manual.
Below are manual test steps. Do: 1) classify each step as automatable, automatable after data setup, or requiring human judgement; 2) write a test skeleton with assertions for the automatable parts; 3) identify the flakiest step that could give false negatives; 4) estimate how long this suite would take in CI. Do not assume a framework exists — state dependencies first.
Site original
Chinese original
How to use
能自动化的先自动化，「人工判断」留给人。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.