Create a Test
Run Tests on a Schedule
Run Tests on Vercel Deployment
Run Tests on Netlify Deployment
Run Tests on Heroku Deployment
Run Tests on Render Deployment
Run Tests with API
Run Tests with CLI
Invite Team Members
Use Environment Variables
Reuse Helper Code
Receive an Email
Call an API
Get a Value
How QA Wolf Picks Selectors
This guide provides a strategy for getting started with testing. It is written for teams who do not yet have automated end-to-end tests.
You may be wondering if automated testing is worth it, especially if you don't have tests now.
We struggled with the same question at our previous jobs. But after building QA Wolf and using it to test QA Wolf (meta), we can confidently say that we are glad to have automated tests.
As developers, automated tests help us ship much faster. Before, we would have to manually check that our critical workflows weren't broken on every release. Now we can test all of our features in just a few minutes.
Automated tests also positively impact your company. It is much easier and cheaper to fix a bug if you find it before a customer does. In addition, customers are more likely to pay for and recommend a high quality product.
The first step is to commit to trying automated testing. We recommend giving it one week to see how it goes. With QA Wolf, you should be able to set up your first test in a few minutes.
After a week, you can reevaluate whether you want to continue with automated testing.
Now that you're committed, let's get started! 🏁
Start by thinking of a single test to run on production. This test should cover a workflow that is core to your product. Here are few examples:
Now create a test for the critical path you chose. Learn how to create a test with QA Wolf here.
After you've created your first test, run it on a schedule. This helps ensure that your critical paths aren't broken.
We recommend running your test once a day to get started. Learn how to run a test on a schedule here.
As you get more comfortable with automated testing, you can add a few more tests. While QA Wolf does support cross browser testing, we recommend testing on just Chrome until you know your tests work.
For many teams, running tests on a schedule is enough. After setting up a few tests on production, you can also schedule them to run on staging. This helps catch bugs earlier in the development process.
You can also run your tests every time you deploy. By running your tests on deployment, you can quickly catch issues with specific releases.
If you have a different deployment process, you can also trigger your tests by calling the QA Wolf API.
🎉 Congratulations - you're running automated tests! You're well on your way to shipping a high quality product faster.
If you need ideas for your next test, check out our guides for inspiration.