Overview

The Sites and Environments page is where you configure the Sites (web sites, applications etc) that you want to test and the Environments you want to test them in (QA, Staging, Production).

Navigation

To get to the Sites and Environment page, select the following:

  • Settings (gear on left green navigation)
  • Sites

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.

Environments consist of 

  • Environment name
  • Webhook URL (optional) - see webhooks
  • Make default option

To set up an Environment

  1. Click New Environment
  2. Enter Environment name.  This can be any name you wish
  3. Enter Webhook URL (optional)

Each Environment created will be available for use for each Site.  

To edit an Environment

  1. Select the Environment
  2. Make changes in the popup

To delete an Environment

  1. Select the Environment
  2. Select the Trash Icon in the popup

NOTE: you may not delete the default environment.  To delete, make another Environment the default first and then delete the intended Environment

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.

To Create up a Site

  1. Click New Web Site
  2. Enter Site name.  This can be any name you wish
  3. Enter the default URL of the Site.  This needs to be a fully qualified URL, ending with the TLD (like .com). The rest of the URL is added in the test.
  4. Click CREATE

Each site will show a separate entry for each Environment and but default to the URL provided when you set up the site.

To change the URL of the site for a specific environment - such as (qa.mysite.com for the QA environment and www.mysite.com for production) select the EDIT pencil and simply update the url.

To make a particular Site the default Site, click the Make Default link (you must have selected the EDIT pencil prior).  This site will now be the default Site when writing new tests.  

Once done with Site edits select DONE

To delete a Site, select the Trashcan icon

The following shows two Environments QA (the default Environment) and three Sites, with Rainforest App the default 

Apps

Apps are similar to Sites but are for mobile applications.  They are configured the same way as sites but have an additional Type component.  

Type options are

  • iOS VM
  • iOS Real Device
  • Android VM
  • Android Real Device

NOTE: We have sunsetted our offering of real devices and only support them for legacy customers.

Environments work the same way with Apps as they do with Sites.

Additional Site Preferences

Allows you to enable Test Redirection by Default.

Using Sites and Environments in Rainforest

Choosing a Site

When you create a new test, it will be for the default Site. You can change it to any other Site with the dropdown under the test’s name. We show the URL of the default Environment for the Site, but the actual URL will depend on which Environment you choose during the run.

Choosing an Environment

When starting a Run, you select what Environment to do the tests against. Otherwise, it will be the default Environment. Whatever Environment you choose, that Environment will be used for all Sites in that run. Each test will use its selected Site and the run’s Environment to determine what URL to start at.

Did this answer your question?