Finish as you wish to Start

Before you finish recording your test, clean up everything you did in the test. If you run an online shop and in the test you log in, Add something to the cart then check the total. The next time we run that test, there will already be something in the cart - so the total of the cart will be different. So at the end of the test, remove that item from the cart. End clean.

Plan your test starting criteria

Generally, most tests either fall into one of two categories:

  • Working with existing data
  • Working with a clean slate

Working with existing data

For this test, you'll want to record a login test, then you can attach that to any future tests. This means you can create a test account with pre-populated data. Then use this data in the tests. Then, for each test, you should end clean, as I mentioned above. This makes each test much better by reducing its impact on other tests.  

Working with a clean slate

If you want to start your test as if you'd just onboarded to your product, you can record yourself getting through the onboarding process - then use that test as your 'login test'. This means every time we run the test we'll register for an account, then run the test you recorded. 

Bonus: you don't need to clean these tests up at the end. Unless you want to delete your account.

Keep tests small

When recording a test, it can be tempting to record as if you're doing exploratory testing. In most cases it is best to keep tests small. Test one small thing, get in and out. 

You should do this so you know when a test fails, you know what to look at immediately. If you record an end-to-end test with 100s of steps and it fails at step 23, you have no idea if what you did at step 23 was the only thing wrong. 

This is why we give you a lot of tests in every plan we offer - we want you to use them.

Did this answer your question?