Running a step
- Find your next step. Open My Work (or your playlist in the app). Work in order within a suite: later steps often depend on earlier ones.
- Check the environment and the account. Confirm you are on the Environment the step expects, and signed in as the right role. Setting a status while signed in as the wrong role is the commonest cause of a false Fail.
- Read before you touch anything. Read What to do and Expected result first, so you know what to look for.
- Do exactly what the step says. If a detail is unclear, do the most obvious reading and write the ambiguity in Result Notes.
- Compare and decide. Compare what happened with the expected result and pick a status using the table below. If you are unsure between two, ask in the group chat rather than guessing; it takes thirty seconds.
- Record it. Tick in the app, then in Test Runs set Status, Environment, Tested On, and notes if anything was unexpected.
- If it failed, write the defect now, before moving on — see Reporting a bug. A failure written up an hour later is half as useful, because the details fade.
Deciding the status, quickly​
| What happened | Status |
|---|---|
| Matches the expected result | Pass |
| Matches in meaning, wording slightly different | Pass, and note the wording |
| Does not match, or an error, freeze or crash | Fail, and write a defect |
| Works, but something else on the screen is wrong | Pass for this step, and a separate defect for the other thing |
| Could not attempt: an earlier step failed, or a build, account or device is missing | Blocked, and say what is missing |
| Chose not to do it, reason is not a bug | Skipped, and say why |
| Started, waiting on someone else | In Progress, and finish it the same day if you can |
The full definitions, with examples, are in Terms you will hear.
One step, one result
A step gets exactly one status. If a step seems to need two — it passed and something was wrong — the step passed and the wrong thing is its own defect, filed against the nearest Step ID.