Steps, checks and values
How to write steps the tester can follow and checks it can judge, and how to have it read values for you.
Steps#
Steps are what the tester does, in order: open a page, search, click, fill in a form, upload a file, sign in. Keep each to one action. A plan holds up to 30 steps.
Checks#
Checks are what must be true for the test to pass. Each one is judged on what is visible on the screen, and the result keeps the value it was decided on and where it was read. Good checks name the text, value or state that shows they passed:
| Instead of | Write |
|---|---|
| The cart works | The cart shows 1 item |
| The price is correct | The cart total equals the product price shown on the product page |
| Sign-up works as expected | After sign-up the page says "Check your email" |
A plan holds up to 20 checks. A check under four words, or one with words like "works", "correctly" or "as expected" and no quote or number, is flagged in the plan.
Values to record#
Values the tester reads and reports even when no check depends on them, such as an order number or a delivery date. They appear in the result under Values seen, with the step they were read at. Up to 12.
Assumptions#
What the plan takes for granted, for example "the pricing page is public". Remove one if it is wrong; the assistant may then ask a question instead.
Questions#
When something only you can answer stops the plan (which account to use, which product to buy), the plan asks. A test with an open question cannot run: answer it, or skip it to run with the assumption.