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.

Setup and Configuration

Sites

Sites are your different web projects. They’re web apps or static sites with different domain names or subdomains such as www.yourcompany.com and blog.yourcompany.com. Every Site has a URL for every Environment.

Environments

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.

For specific information on Setting up Sites and Environments click here.
Access your Sites and Environments page in-app.

Setting Default Platforms / Browsers

Set the platforms you’re going to be testing against the most selecting them in your Platforms settings.  This will save you time later on so you don't have to constantly select the browsers / platforms you want to test against.  You can customize or override your default Platforms for any individual test, but it’s easiest for your test writers if default browsers are preselected.

For specific information Setting Default Platforms / Browsers see here.
Access your Platforms page in-app.

Create Test Accounts

Spin up test accounts

Create enough login credentials for testers to execute tests requiring logins to your web application. After these accounts have been created, upload them to Rainforest as tabular variables as a Comma Separated Value (.CSV) file. When a test is run, each tester will be assigned one unique row of variable 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.

Reach out to us at support@rainforestqa.com if you have questions on best practices for managing seeded states.

Invite your Team

For information on managing and inviting your team to use rainforest, see here 

Writing & Executing Your First Tests

  1. Define Your Smoke Tests 
  2. Build Your Initial Test Suite
  3. Run your 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.

View your 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.

Build your Regression Suite

To start building out your regression test suite, we recommend checking out:

Create a process to update and optimize your test suite

Read how we at Rainforest have optimized our usage of Rainforest.

Questions?

Our Help Center is always available and will likely have the answer to the question that you have. If you need further assistance, reach out to us by clicking the blue chat icon wherever it appears in the Rainforest portal or email us at support@rainforestqa.com.

Did this answer your question?