Recording well
How you record changes the quality of the specification and test cases you get.
One scenario per recording
Section titled “One scenario per recording”This matters most. If you record sign-in through checkout in one go, only some of the test cases get created.
| Works well | Avoid |
|---|---|
| One recording for “sign in”, one for “choose an item”, one for “check out” | One recording from sign-in to order confirmation |
A scenario is a continuous set of steps with a single purpose. Keep one recording to one of them.
Work at a steady pace
Section titled “Work at a steady pace”Wait for each screen to finish loading before your next action. Acting mid-load can leave gaps in the capture.
Put what you want to check on screen
Section titled “Put what you want to check on screen”Autest builds the specification from what is visible. If you want to check that an error message appears, trigger that error while recording.
Use dummy data
Section titled “Use dummy data”Do not enter real personal information. What you type is recorded and used when generating the specification.
Prepare test email addresses, addresses and phone numbers, and use those.
Stay in the same tab
Section titled “Stay in the same tab”If a link opens in a new tab, what you do there is not recorded. Go back and continue in the same tab.
When in doubt, record again
Section titled “When in doubt, record again”Recording is repeatable. If it did not go well, choose New recording and do it again. You can delete recordings you do not need.