Prepare your Sites and Environments for testing with Rainforest

Setup and Configuration

1. Configure your Sites and Environments


Sites are distinct web properties which you’d like to run Rainforest tests against. All new tests created in Rainforest will be set to run against the default Site as configured in your Sites and Environment settings.


Your web app might be deployed to multiple locations—such as a staging, develop or production environment. If access to your environments are restricted by IP address, please see our list of IPs to whitelist so that our testers will can gain access for testing.

2. Select your default Platforms
Let us know the testing platforms you’re going to be testing against the most often by selecting them in your Platforms settings. 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.

3. 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.

How many test accounts do I need?

Be sure to create sufficient accounts so that all testers assigned to your test will receive a unique account. Use the following equation to ensure that you will have sufficient unique accounts:

Minimum number of test accounts:

Tests * Browsers * (3 Testers * 2 Safety)

  • tests = number of tests using this variable
  • browsers = number of browsers you're running these tests against
  • testers = default number of testers we send to each job
  • safety = safety margin we use in case we need to add more testers to a job

Using this equation, to successfully run 1 profile update test against 5 browsers, the we would need a minimum of 30 logins.

4. 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.

5. Whitelist Rainforest's VM IP List
While there are a number of ways to grant access to your environments, the most commonly used method is whitelisting the IP ranges of from which Rainforest VMs come from.

To view our most up to date list of IPs, please see our documentation here. This list can also be fetched programmatically through our API. Learn how to do that here.

If you have any questions, please feel free to reach out to us at or through Intercom!

Did this answer your question?