Results and reports

Check how many scenarios passed, failed, or did not finish. Confirm that the run covered the intended release journey before reading the score.

1. 1

   Open the first failed step

   Later failures can be a result of the first problem.

2. 2

   Compare expected and actual

   Check what the scenario expected and what the browser found.

3. 3

   Assign the cause

   Decide whether the issue is in the product, test, data, or environment.

Use screenshots, step details, status, and timing together. A screenshot gives context, but it does not replace a clear expected result.

Record what is blocked, who owns the next action, and whether another run is required. A report is useful when it leads to a clear next step.