What is a step?
How specific should my steps be?
Tests must be tightly focused on an specific process, but individual steps can be as high level or low level as you wish, depending on what you want to confirm.
Let's look at this test for a signup form.
If the only level of detail that is important to us is the successful creation of a new user, the following step would be perfectly fine:
Each step should be an easy-to-follow instruction of what the tester should do, followed by a clear question confirming what they should expect to see. Be sure that this question can be answered with a Yes or No.
Some tips for writing awesome steps:
1. Draw attention to important terms with quotes.
Rainforest testers are trained to enter or look for terms in quotes exactly. This is a easy way to indicate to testers that you need to confirm that your copy is exact, or have them enter specific text into a field.Instead of:
3. Eliminate jargon
The best Rainforest tests are free of jargon. We always imagine that we're writing our tests for our grandmothers to perform.
Take a look at the difference:
The simpler and more user-friendly your language is, the faster and more reliable your results will be.
4. Keep step instructions simple
It's easy to lose track of what to do next when steps are dense. If you find you're including 3 or 4 different instructions in a single test, it's better to break them into two.
This is a little hard to follow:
This is much more clear!
5. Embed image and text files:
If you would like testers to look for something that might be difficult for them to understand or if it's complex for you to describe, consider adding an image into the step so they know exactly what to look for. The same works for a text file—just drag and drop them into the step!
Questions? We're here to help!
Want some more advice on writing your steps? Looking for suggestions, tips or tricks? Reach out to our team at firstname.lastname@example.org!