How to use the Usability Test Script Generator.
Usability tasks should express a goal without revealing the interface path. Define success in observable terms before running the session.
Make the workflow fit your task.
Give participants a realistic goal without naming the controls they should use. Define observable success, expected evidence and neutral follow-ups before the session, leaving room to record unexpected paths.
- What you provide
- Prototype goals and target users.
- What you get
- Task-based moderator guide and success criteria.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Test whether users can find a changed price in a comparison view.
Completed example
Task: identify which product needs review. Success: the participant finds the changed row and explains the difference.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a usability task tell the participant which button to click?
Avoid revealing the path when discoverability is being tested. State the goal and let the participant choose how to reach it.
Why are all participants succeeding without revealing usability problems?
Check whether the task gives away interface labels or steps. A leading instruction may test compliance rather than independent use.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑