You've signed up and you're ready to start firing off your first Rainforest tests. To generate the best, most deterministic results, there is a bit of setup that must be completed as soon as possible.

These configuration steps are essential, and should not be delayed or overlooked. Proper testing configuration ensures that any errors that you receive are meaningful. A staging server configuration that differs too much from production, or cannot support tester traffic will not meaningfully reflect a user experience, and may generate inaccurate results.

Make sure that the following are in place and you'll be in great shape to start testing!

Most tests should be run against a staging or QA environment

The environment that you run your Rainforest tests against should reflect production as accurately as possible.  

  • Infrastructure - software versions, configurations, etc
  • Realistic test data - fake user accounts, fake products, fake datasets
  • Application - code base, server configuration, etc

All of the above should be nearly identical to the user experience in production. If this configuration differs too much, your results may not be representative of a real-world user experience.

Testers must be able to access your testing environment

You may have one or more levels of security restricting access to your staging site.  Some simple solutions within Rainforest to bypass common access control methods are:

IP access controls - Whitelist our VM IP addresses

HTTP basic auth - Add a step to each test to give testers login credentials. Alternatively, configure your test URL to include the username/password, and allow testers to access your staging site with no extra effort. 

Custom authorization layer - Create a standalone test directing users to sign in with a defined username/password. In most cases, testers can use the same credentials. Embed this as the first step in all subsequent tests to save time.

SSL Certificates - Rainforest can help you create valid, self-signed SSL certs here

  • Simply enter your domain and then install the cert.
  • Wildcards are supported, so you can configure your domain in any way you require: '*.yoursitename.com'

Account for tester load on staging server

Large test runs will generate a lot of traffic on your staging site.  You will want to make sure that your infrastructure can accommodate this traffic; i.e. your servers are fast enough, have enough CPU and memory, etc.  Ensure that you have sufficient:

  • Network bandwidth
  • Firewall capacity 
  • Server capacity 

Did this answer your question?