The short answer
A visible button may not work, and a generated file may contain errors. Document actions and expected outcomes to judge completion.
Try it in three steps
- Write one normal usage path.
- Add empty input, repeated clicks and return navigation.
- Record outcomes and exact failing steps.
A practice prompt
Before you start
Write expected results first and fill actual outcomes only after execution.
Practice material (fictional)
Blank-line remover: ordinary input, whitespace only, two consecutive clicks, then return to editing.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
Create an acceptance table with input, action, expected and actual results for normal, empty and long text. Leave actual results blank.What to look for (not a recorded test result)
Specify content, empty handling, repeatability and input retention without marking unperformed tests passed.
If it goes wrong
Passing labels without execution are assertions, not test records.
Check your result
Another person can reproduce the result and identify untested cases.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.