This guide will provide you with a high-level overview how the Rainforest platform works, and how to begin your journey with Rainforest testing. We know testing is not always fun or easy, but don’t worry, you are not in the QA jungle alone.
Getting started is pretty easy, there are three main areas:
- Setup Sites & Environments
- Set Default Platforms / Browsers
- Create Test Accounts
- Write & Execute Tests
- View & Categorize Results
Sites & Environments
Sites are your different web projects. They are web apps or static sites with different domain names or subdomains such as www.yourcompany.com and blog.yourcompany.com. You can set up a different site configuration for each.
Environments are the stages along a deployment pipeline. They’ll usually have names like Dev, QA, Staging and Production. When you run a group of tests, they run against one Environment. Each Environment can optionally have a webhook.
Default Platforms / Browsers
Set the platforms you’re going to be testing against the most by selecting them in your Platforms settings. This will save you time as you won't have to constantly select the browsers/platforms you want to test.
For specific information Setting Default Platforms / Browsers see here.
Access your Platforms page in-app.
Create Test Accounts
Spin up test accounts
You will need to create enough login credentials so that when the crowd tests your site they aren't "stepping on each other's toes". This is applicable if your site requires specific login /accounts. For a marketing or informational sites where specific accounts and logins are not required this is less of a concern.
After these accounts have been created, upload them to Rainforest as tabular variables using a Comma Separated Value (.CSV) file. When a test is run, each tester will be assigned one unique row of variable login values, which will be repeated any time the tabular variable placeholder appears within a specific test.
For specific information on How to Create Test Accounts, Add Them to Rainforest QA and Use them see here.
Prepare users with seeded test states
Seeded states allow testers to land into an account that has certain actions complete. With a seeded state, you can have a tester login and go directly to the part of your application you need to test. Having users with various seeded test states is crucial to reducing run time and tester error.
For more information about managing seeded states, see here.
Invite your Team
For information on managing and inviting your team to use Rainforest, see here.
Your team won't be executing the tests, but you will want to be able to help create, manage and kick-off the tests. Your team will also be able to review results and take appropriate actions as a result.
Writing & Executing Tests
There are several ways to run your Rainforest tests:
- Test-level runs: select individual or multiple tests to start a run.
- Run Saved Filters: apply a filter from the Tests view to run tests by Tags.
- Features: run tests manually by feature
- Scheduled runs: set the day and time of when you want Rainforest to automatically trigger runs of your tests based on tags or folders.
- Trigger tests using the API or CLI.
Build your Regression Suite
To start building out your regression test suite, we recommend checking out:
- The Regression Test
- Our list of 50 Essential Integration Tests that may be applicable to your application
- How to leverage our Developer Experience which allows your developer team write and upload tests via our CLI without disrupting their everyday workflow
- Our CTO's guide to Continuous Deployment
See Working with Test Results for detailed information on test results
It is important to understand how and when Rainforest rejects or accepts tester results. Review this short explanation that will explain how it works.
Create a process to update and optimize your test suite
Read how we at Rainforest have optimized our usage of Rainforest.
If you need further assistance, click the blue chat icon in the Rainforest App or email us at firstname.lastname@example.org.