Welcome to Rainforest QA
Rainforest QA is modern testing for web and mobile apps. The Rainforest platform delivers all the resources needed to do fast, efficient QA. We combine a massive crowd of human testers with algorithmic management and VMs to execute web and mobile regression testing for continuous deployment.
This guide will provide you with a high-level overview how our 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.
Here is what we will cover:
- The Basics
- Setup and Configuration
- Sites and Environments
- Invite your Team
- Test Cases
- Test Writing
- Test Management
- Run Tests
- Interpreting results
- Documentation and Support
Rainforest primarily revolves around test cases, created by our customers (most likely you), which are written to test your web application or app. We then send those test cases to be completed by our testing crowd. The testers’ responses, actions, and behaviors are analyzed by our algorithm to provide you with synthesized and comprehensive results.
What are Rainforest tests? They are nothing more than a short series of instructions for testers to follow and confirm outcomes. Each instruction, which we call a step, is written in a simple action/question format designed to be both easy to write, and easy to execute.
Since you will likely be working on some aspect of Rainforest, we ask you begin by watching this short introduction of the Rainforest QA Dashboard. It will address most questions new users have.
Setup and Configuration
STEP 1. Configure your sites and environments
From the Menu, click on Sites
You can configure Rainforest to test again any number of sites. We think about sites as distinct web properties which you’d like to run Rainforest tests against. By default, all tests can only be run against one single site.
Your web app might be deployed to various locations—such as a staging or production environment. Please make sure to provide us with the correct site URL for your web app in their various environments. If your environment is behind a firewall, see the list of IPs to whitelist for our testers to get access.
STEP 2. Select your default browsers
From the Menu, click on Browsers
Let us know the browsers you’re going to be testing against the most often by selecting them in your browser settings. You can customize or override your default browsers for any individual test, but it’s easiest for your test writers to preselect the default browsers.
STEP 3. Spin up test accounts
From the Menu, click on Step Variables
Create enough login credentials for testers when they’re executing tests that require logins to your web application. Upload a CSV file into your account to configure your step variables. If your tests require unique variables during a run, then tabular variables are a great option. When a test is initiated, each tester will be assigned one unique row of variable values, which will be repeated any time the placeholder is used again within a specific test. See this article for more details or if your unclear is you require them.
STEP 4. Prepare users with seeded test states (Optional)
When you provide testers with an account that has been pre-seeded with data, they’ll be able to land into an account that already 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 the success of your Rainforest testing. This typically requires developer resources so some considerations are important to discuss with your team.
Invite your Team
From the Menu, click on Team
Enter the Name and Email of whoever you want to invite and click 'Invite User':
Your teammate will now get an email inviting them to Rainforest, and be asked to set a password and then logged in. Note that the email link is good for 10 hours.
To remove a user, simply hit the 'x' beside their name and confirm:
NOTE: If you need to modify details of the team member, or need to resend the invite, delete the user and re-invite.
As we mentioned earlier, Rainforest tests are written in steps. What is a step? Your Rainforest tests drive testers through each process via a simple series of action/question formatted steps. Steps are the primary means of instruction to your testers, so it's vital to understand how to write the best steps you can.
Each step is comprised of two parts:
- Action - What should the tester do?
- Yes or no Question - What should the tester see?
This simple format is easy for anyone on the team to write, but also easy to understand and execute. For more information on test writing and what test you should create see our supporting documents on Writing Tests.
Rainforest provides options to organize your test cases.
Apply tags to organize and categorize your tests as you're writing out your tests. For example, you could include a "critical" tag for tests that need to be run every time you deploy, or a "photos" tag for your tests related to the photos functionality in your app. To tag a test, start typing in the TAGS box and hit Enter to save the tag. Learn more about other types of tags you can consider.
By Smart Folders
Smart Folders provide a more granular way to organize your tests. You can define what tests should be included in a Smart Folder by adding a 'Tag condition'. A tag condition could be as simple as: “Include all tests with tag ‘green’”, or “Exclude all tests with tag ‘red’”.
Run your tests
There are several ways to run your Rainforest tests:
- Test level runs: select individual or multiple tests to start a run.
- Filtered runs: apply a filter from the Tests view to run tests by test Result type, Sites, or Tags.
- Smart Folder: run tests manually by folders from Folder view.
- Scheduled runs: set the day and time of when you want Rainforest to automatically trigger runs of your tests based on tags or folders.
The Rainforest algorithm is constantly evaluating and learning from collected behavior and results. Rainforest recruits at least 3 testers for every test. Each tester’s actions—such as mouse activity, time spent on each step, or correct site navigation—are all monitored by our system and compared to one another to ensure consistency.
From the Menu, click on Results
See this article for a comprehensive breakdown of the results sections.
Also, it is important to understand how and when Rainforest rejects or accepts tester results. Review this short explanation that will explain how it works.
Documentation and Support
We have a Help Center that houses all our supporting documentation. We encourage you to search for topics you would like to learn more about. If something is missing, or you think could be more helpful, please let us know.
The Rainforest Customer Success Team is just a click away. From our web application feel free to click on the blue message icon on the bottom-right of the page. From time-to-time, we will communicate important information in through the same system.
Note: Our primary team is based in Pacific Standard time zone, which means we may not always be available to provide an immediate response. However, we will do our best to get back to you as soon as we can.