On-premise testing allows you to leverage your own team to execute test case scenarios through the virtual machines and platforms available via Rainforest.

An on-premise run mimics the steps of a traditional crowd run, but supplants the crowd with your own testing resources with the results and findings stored automatically in Rainforest.

Setting up On-Premise

It is important to note that on-premise is a feature upgrade. If you would like to have this feature enabled please contact support@rainforestqa.com or your customer success manager for access. 

To get started, you must first set up your pool of team members who will be responsible for conducting application testing. To invite users to become part of your on-premise tester community, you must follow the following navigation pathway:

  • Settings → Team → Your On Premise Tester Team

From this view you will have the ability to invite the team members who will be part of your on-premise tester team to join. Do note, that even if a user presently has permissions to the application, they will still require an invitation to join this team as, with it, comes a different set of permissions/actions that are unique to the on-premise experience.

 

After a team member is added to on-premise, they should receive an email similar to the below where they will be asked to set up their testing profile:

Running a test

Now that the on-premise testers have access to their dedicated on-premise account, it becomes time to initiate jobs for these testers to complete. 

To do so, you may navigate to an existing test or run group and select for it to be ran by the On-Premise Crowd

After the run is confirmed, a notification to each member of the on-premise team is sent to their respective inboxes. Once received, they may enter their job portal and begin executing the test in the same manner that our global test crowd does. 

 

Their results will be aggregated and stored within the Rainforest application in the same manner as existing test results run against either the global crowd or Rainforest Automation are returned. 

Key Items of Note

On-premise provides a team with many benefits such as on-demand access to Rainforest’s virtual machines as well as being able to use Rainforest as a de-facto test case management tool. With all the above in mind, however, there are a couple common items a team leveraging this functionality should keep in mind:

  • When a run is initiated it is distributed to your entire on-premise team, not a single tester
  • This makes it pivotal to include internal processes that dictate which team member is responsible for each test and their expected turn around time
  • To review the user who completed a test, you must either use your internal knowledge base, or click into a returned result to see the tester that executed the run
  • Traditional Rainforest crowd tests requires a minimum of three testers to complete each case, however, with on-premise you will only need one tester to complete a scenario for results to be returned
  • One job will be created per browser being tested 
  • I.E. if Chrome HD, Firefox HD, Edge HD and Safari HD are selected for 1 test, 4 individual jobs will be created when that test is run.
Did this answer your question?