Objectives and scenarios

An objective describes what must work, such as “A customer can sign in.” A scenario is the exact set of steps used to prove it. One objective can have a normal path, an invalid-input path, and a recovery path.

Start with tasks that affect users or revenue. Cover the normal path first. Then add validation, permissions, empty states, and recovery only where they protect a real risk.

1. 1

   Name the action

   Say what the user does, such as Select Sign in.

2. 2

   Use safe data

   Use prepared test values, never personal customer data.

3. 3

   State the result

   Describe what should be visible after the action.

Another teammate should be able to read the scenario and explain what it proves. If the expected result is vague, edit it before browser execution.