iOS 14

iOS 14 Beta 4 on iPhone Pro Max 11 now available!

The World is on the move and testing on the latest mobile devices is essential to ensure a smooth experience for your clients. Rainforest now supports iOS 14 Beta 4 on iPhone Pro Max. Extend your mobile testing experience!


For a full listing of all the platforms Rainforest supports see here. To enable this latest mobile offering, please see your CSM or contact support at

Detailed Test Writing Service & Exploratory information

See how you've benefited from Rainforest Exploratory and Test Writing Services.

We've updated the information on the Exploratory and Test Writing Services usage cards so you can see exactly how you have used these services. The exploratory card shows how much time Rainforest testers have spent searching for potential issues on your site and how many bug reports they have generated. These are actual Rainforest tests that you can continue to run and update to increase your test coverage.


The Test Writing Services card now details how many tests Rainforest has written and re-written so you can see exactly how much time you have been able to save your team by offloading these activities to Rainforest.

See more information on Test Writing Services and Exploratory testing or contact

Quicker Rainforest Automation

A more responsive experience writing Rainforest Automation tests.

Rainforest Automation is No Code Automation Testing. We continue to improve the test authoring experience. We've enhanced our infrastructure, making instant replay quicker and more reliable. Selection of actions and starting, stopping of Instant Replay is quicker, making your test writing experience easier.

For additional information on Rainforest Automation - see here or contact

Test Writing Service browser selection

Request Test Writing Service (TWS) on any browser

You may now use any browser that is enabled for you to request Test Writing Services.

Use Rainforest Test Writing Service to initiate a new test writing request, import tests from TestRail, request a test to be rewritten or convert your test to Rainforest Automation. We have specially trained testers (test writers) create and update your test cases using high-level test outlines about the desired tests to receive passing tests within a few days.


See here or contact for more information.

CI Sample Repo

More CI workflow samples, making it easier for you to include Rainforest tests into your CI workflow

Incorporating Rainforest tests into your CI workflow adds value by allowing you to test earlier and more often, catching issues earlier on the process when they are easier and less expensive to fix. We have added examples of how to integrate Rainforest tests into your CI workflow to make the process as easy as possible. See our updated CI Sample repo for examples and detailed information.

Screen Recording 2020-08-11 at 03.20 PM.gif

Examples and information is provided for Circle CI, Jenkins, and Travis that need simple modifications for your use.

Rerun failed tests via the CLI and CircleCI

Now when a Rainforest run reports failed tests in CI/CD - retest only those failing tests.

The latest version of our CLI, v2.16, adds a rerun command which behaves exactly like the “Rerun Failed Tests” button on the Test Results page in the application.

As with the rest of our CLI this was built with CI in mind. Use the rerun command when retrying CI builds to significantly shorten your time to release.

This functionality is baked into the latest version of our CircleCI orb, v2.0, to automatically rerun failed Rainforest tests when rerunning a failed CircleCI workflow.

Rerunning a single failed test rather than our full release suite

Read more about our CLI and CircleCI integration in our Help Center.

Rainforest Automation Content Matching

We are reducing brittleness by adding additional ways to identify elements beyond the pixel matching we do today.

When you create a new action or recapture an element in a Rainforest Automation, we will automatically analyze the image and use our content matching if possible. Content matching means that as long as the text content stays the same, the test will pass, even if the appearance of the changes.

Screen Recording 2020-07-02 at 05.20 PM.gif

If exact visual appearance is important, you can turn off content matching for that step and we will only look for the element using pixel-based matching. We're continuing to add flexibility and intelligence to reduce brittleness and test maintenance.

Screen Recording 2020-07-06 at 09.07 AM.gif

We've made image capture easier too. No simply click on Screen Capture. No need to click the camera when capturing an image!

For more information see our help center.

VM Notification to Support

As part of our continuing focus on delivering great customer experience, we’ve introduced a program to investigate all the test failures that you categorize as a “System issue” with “Rainforest virtual machines or devices” to see whether the failure was an issue with the Rainforest platform and see what we can do to stop it from happening again.

We’re doing this to reduce the number of false failures and save you more time to concentrate on the important things in life!

You can find out more about categorizing test failures in this document.

New and Enhanced Charts

More metrics and charts to help you monitor and improve quality.

People measure and track Quality differently. Rainforest's new and more robust reporting charts help you slice and dice the data that’s most important to you. You want to track the health of test suites, team engagement, and value over time.

We've improved charts by:

  • adding time filtering - so you can zoom and hone in on the time periods you care about to spot patterns and trends over time
  • adding more metrics that you have wanted. You now have details on average run times, %failures by jobgroup (rather than by run), % failures categorized over time, and browser/platform usage.

We've added new reports so you can further dive into your test suite:

  • Tests created/updated over time - RFA vs. Plain English
  • Average run times - RFA vs. Plain English
  • % Failures - RFA vs. Plain English

We have also updated how we represent failed runs so you have a clearer insight into failed tests. Previously, we provided % failed RUNS (which means that if 1 test in a run of 500 tests fails, the whole run is counted as a failure). One test failing in a group of 500 is much different than 50, 100, or more. Now you can see the details more accurately.

For more detailed information on Rainforest Reporting, see Rainforest Help Center.

Rainforest Automation

We had previously called our no-code automation language "Rainforest Test Language". We renamed it "Rainforest Automation" so it's clear whether you are using our crowd for manual testing or our virtual machines for automation tests.

Rainforest Automation is an easy to use, no-code automation solution that is fully integrated with the Rainforest platform. You may create tests yourself or have our Test Authors create them for you via our Test Writing Services.

Additionally, Rainforest Automation tests may be executed via our automation bots or by the Rainforest Tester Crowd, giving you additional options and flexibility on how you manage your test suite. For more information, please check our help center here.