Rainforest Tests: Executing tests

Rainforest tests can be executed using Automation Services, Tester Community, and On-Premise Testers.

📘

Rainforest vs. Rainforest Classic

Rainforest Automation and RFA are now Rainforest tests.

  • Rainforest Tests - Quickly capture UI element with screenshots
  • Rainforest Tests provide easy and efficient test writing for desktop applications. Test execution may be done via Automation Service, Tester Community, or On-Premise Testers.

Plain English tests are now Rainforest Classic tests.

  • Rainforest Classic tests - Detail your test case line by line
  • Rainforest Classic tests allow you to write instructions via a free-form English testing writing interface. Tests may be run on desktop applications, mobile browsers, and mobile applications. Test execution is done via the Tester Community or On-Premise Testers.

Overview

Rainforest tests are flexibile and can be run by the Automation ServiceAutomation Service - Automated browser execution of tests. The quickest and most cost-effective way to get test results, powered by our network of virtual machines., Tester CommunityTester Community - Human execution of tests. Harness the ingenuity of on-demand QA Testers. Pay more and wait longer to get test results but get a more detailed output., or On-Premise TestersOn-Premise Testers - Use your own team of in-house testers to get test results..

Rainforest automatically updates the available run method options based on the test(s) being run and the execution options available. ​Individual tests may be run using:

  • Automation Service
  • Tester Community
  • On-Premise Testers

See our article on Run Test Dialog for step-by-step details on how to start a run for a single test, multiple tests, features, and run groups.

 

Run Methods for Rainforest Tests

Automation Service

  • Automated browser execution of tests.
  • The quickest and most cost-effective way to get test results, powered by our network of virtual machines.

NOTE: Available for any Rainforest test that does not contain a Tester Instruction or Tester Confirmation step. See Rainforest Tests: Actions, Assertions and Embedded Tests for more information.

Tester Community

  • Human execution of tests.
  • Harness the ingenuity of on-demand QA Testers. Pay more and wait longer to get test results but get a more detailed output.

Automation Service + Tester Community

  • Run tests using a combination of the Automation Services and the Tester Community.
  • Tests that can be run using Automation Services will be run using the Automation Services.
  • Tests that cannot be run using the Automation Services (contains a Tester Instruction or Tester Confirmation step) will be run using the Tester Community.
  • Tests will automatically be assigned to the appropriate run method, no need to manually determine which test is run which way.

On-Premise Testers

  • Use your own team of in-house testers to get test results.

Note: On-Premise Testers is an additional service. For more information see our article on On-Premise Testing.

 

Running via the CLI

Start run groups via the Rainforest CLI with the following commands.

Rainforest Automation + Tester Community

rainforest run --run-group <run group number> --crowd automation_and_crowd

Rainforest Automation

rainforest run --run-group <run group number> --crowd automation

NOTE: Available for any Rainforest test that does not contain a Tester Instruction or Tester Confirmation step. See Rainforest Tests: Actions, Assertions and Embedded Tests for more information.

Rainforest Tester Community

rainforest run --run-group <run group number> --crowd default

On-Premise Crowd

rainforest run --run-group <run group number> --crowd on_premise_crowd

Note: On-Premise Testers is an additional service. For more information see our article on On-Premise Testing.

See our CLI documentation, visit this link.

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

Updated 2 months ago



Rainforest Tests: Executing tests


Rainforest tests can be executed using Automation Services, Tester Community, and On-Premise Testers.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.