Plans & Pricing

Yes. After the 14-day free trial, if you decide not to enter a credit card to unlock premium features, you’ll continue to have access to all of the non-premium Professional features listed above. That means you’ll have everything you need for no-code automated testing, for free — no credit card required.

Even if you enter your credit card to unlock premium Professional features, there’s no subscription fee. The only time you’ll pay is if you run more than five hours of automated testing in a month (each additional hour is $5/hour) or if you use our QA specialists for manual testing ($25/hour).

*Some of our enhanced testing features like mobile native app testing and on-premise testing are available for an additional fee.

During the free trial, you’ll be able to try everything in the Professional plan — including premium features — at no cost, with no credit card required.

That means, for example, you’ll be able to get on-demand manual testing from our worldwide community of QA specialists, free of charge. (After the free trial, that premium feature is $25/hour.)

Certain premium features are only available for free during the 14-day free trial. After the free trial, you’ll continue to have access to all of the non-premium Professional features listed above. You’ll still have everything you need to write, run, and maintain no-code automated tests for free.

To unlock premium features after the free trial, simply enter a credit card in your billing page. There's no subscription fee.

You don’t need a credit card to get started, or to have ongoing access to all of the non-premium features available in the Professional plan.

The only time you’ll need to enter a credit card is if you want to unlock these premium features. (There's no subscription fee.)

• On-demand manual testing by our worldwide community of QA specialists
• Mobile web testing by our QA specialists.
• Older versions of browsers including Chrome, Firefox, Edge, Safari, and Internet Explorer.
• Older versions of operating systems and platforms. Test on the latest and previous versions of desktop OSes (Windows, MacOS) and mobile OSes and devices from Apple and Android. 
• In-app chat support.
• 30 days of help getting started from an implementation expert on our team.

To unlock all of these premium features in Professional, simply enter your credit card details in your account at any time — there’s no subscription fee: 

• On-demand manual testing by our worldwide community of QA specialists
• Mobile web testing by our QA specialists.
• Older versions of browsers including Chrome, Firefox, Edge, Safari, and Internet Explorer.
• Older versions of operating systems and platforms. Test on the latest and previous versions of desktop OSes (Windows, MacOS) and mobile OSes and devices from Apple and Android. 
• In-app chat support.
• 30 days of help getting started from an implementation expert on our team.
  
  

You can start writing your first Rainforest test immediately after signing up. Since we provide all the testing infrastructure you need, the only setup you’ll need to do is entering the URL of the website you’d like to test. 

Once you’re ready to run your tests, it’s as simple as pushing a button and choosing which environments (browsers / operating systems / devices) you want to run your tests on. In as little as a couple of minutes, you’ll have comprehensive test results including regression steps, HTTP logs, and video recordings of every test.

Based on your needs, you might want to make additional configurations. These are the most common:

• Add your staging and/or QA environments to Rainforest
• Upload your own test data
• Add Rainforest tests to your CI/CD pipeline
  

Unlike Selenium, Cypress, and similar code-based frameworks, our proprietary testing automation doesn’t require any coding, so anyone can use it to write, run, and update automated tests. You don’t need to hire an expensive engineer to manage your automated test suite.

Many other “no code” solutions are simply a front-end wrapper around Selenium. You might not need code to create a test, but you’ll need coding skills to update any tests. (And every QA tester knows that test maintenance is an ongoing exercise.) The Rainforest automation product was built from the ground up to support no-code usage in every step of the testing process: writing, running, and updating tests, and evaluating test results.

Finally, in spite of what they’ll tell you, Selenium-based solutions do not do true user interface (UI) testing. Their tests don’t interact with the UI of your app; they evaluate the underlying code ("the DOM”). There are two major implications of this approach:

• DOM-based tests can miss issues that’d be obvious to your users. For example, a DOM-based test that confirms the presence of an important button (like the signup button) could pass, even if the button is inadvertently blocked by a popup. Only by interacting with the UI (not the underlying code) would you see the issue.
• A DOM-based approach adds extra brittleness to tests. If someone changed the code-based name of a button from “signup_button” to “signup_button1”, for example, a Selenium test looking for the button could fail — even if the button still exists. That means someone with the right coding skills would need to find the part of the test that needs to be updated and then fix it. 

Unlike DOM-based solutions, Rainforest automated tests interact with the actual UI of your app, so you can be confident that you’re testing exactly what your users and customers will experience. Any changes you make to underlying code that don’t affect the UI won’t break Rainforest tests. Rainforest tests are designed to fail only when your UI doesn’t match “passing” expectations. It’s true UI testing.

Many product teams struggle with the right balance of automated vs. manual testing. A good test strategy involves the right application of both methods. Here’s how we think about it:

Automated testing is best for the mindless, repetitive tests that you find yourself running over and over again on stable features of your app. (Computers are great for mindless, repetitive tasks.) These typically include smoke tests and regression tests.

Manual testing by humans is perfect for the tests that can’t — or shouldn’t — be automated. 

• For frequent UI changes: Do you want to test a new part of your app that’s subject to ongoing user interface (UI) changes? People are flexible and can roll with frequent changes, whereas automated tests would have to be updated for every UI change, no matter how small.
• For subjective feedback: Do you need subjective feedback like, “Do the images look clear?” Then you need the subjective judgment you can only get from human testers. 

Our community of human testers can follow any of the step-by-step test cases, or “test scripts”, that you create in Rainforest. On the Enterprise plan, we also offer an exploratory testing service, in which a group of our testers will explore your app in an unscripted way, trying to uncover bugs and edge cases not covered by your test scripts. 

On the Rainforest platform, automated testing of mobile experiences is in early beta, so you’ll want to run those tests manually with our tester community, too.

Want to learn more? We go deep on this subject in this article.

The basic version of Professional (excluding premium features) includes the latest versions of desktop operating systems and browsers:

• Operating systems: Windows 10, MacOS 10
• Browsers: Chrome (Win), Firefox (Win), Edge (Win), Internet Explorer (Win), Safari (Mac)
  

The premium version of Professional and the Enterprise plan include the latest and previous versions of operating systems, browsers, and device platforms:

• Operating systems: Windows, MacOS, iOS for iPhone and iPad (simulators), Android Phone & Tablet (virtual devices)
• Browsers: Chrome (Win, Mac, Android), Firefox (Win, Mac), Edge (Win), Internet Explorer (Win), Safari (Mac, iOS)

Here’s the full list of 40+ browsers, OSes, and virtual devices supported on Rainforest.

Yes, our QA testers can manually run your tests across any combination of browsers.

A test created for automated testing on Rainforest will typically work best on the browser on which it was created. For example, if you create an automated test using Google Chrome on Windows 10, that test will run best (i.e., without “false positive” test failures) on Google Chrome on Windows 10. 

The reason for this is that automated Rainforest tests use pixel-matching to look for and identify UI elements on a page. This allows us to do true UI testing and evaluate your app in the way your users will experience it. (Compare this to many other automated testing frameworks that claim to do UI testing, but actually evaluate the code underlying the UI. This approach can miss actual UI issues and cause tests to fail when minor behind-the-scenes code changes are made.)

Because every major browser (Chrome, Firefox, Safari, etc.) renders the UI of a web page slightly differently, automated Rainforest tests might not locate an element (like a button) in one browser that appears differently in another browser.

Yes, we support manual testing of mobile experiences via our community of QA specialists. Test automation on mobile is not officially supported.

Native mobile app testing is included in the Enterprise plan and is available in the Professional plan for an additional fee.

The simulators and virtual devices in our cloud-based infrastructure include the latest and previous operating systems, phones, and tablets from Apple and Android. (We don’t test on real devices.) You can find the full list of supported mobile configurations on this page.

No, for several reasons including scalability, speed, security, we only run tests on virtual machines (VMs). 

Thanks to the wide availability and affordability of cloud-based computing power, we can spin up any number of VMs to meet your testing needs in real-time. You can run any number of tests in parallel on our VMs and you don’t have to pay extra for using extra machines — you only pay for the fixed hourly price of testing. Compare that with 3rd-party testing grids like BrowserStack that get (much) more expensive as you do more automated testing in parallel.

We spin up a clean VM for every test, which is faster and easier than resetting a physical device every time you want to run a test. After a VM is done running a test, we destroy it, along with any of your sensitive test data.

Because we don’t test on real hardware, we can’t help you test hardware-specific features like video recording, audio recording, taking photos, and using non-spoofed location services.

We run the tests from every test suite in parallel, whether the tests are executed by our automation service or by our worldwide community of QA specialists, who are available on-demand, 24x7. 

Even if you kick off a test suite containing 500 tests, we'll run all of those tests at the same time. That's how we can deliver test results from automation in 3.5 mins, on average, and from our community of testers in 17 minutes, on average.

Yes. Rainforest was built from day one to work within continuous integration and continuous delivery workflows. (In fact, we think implementing CI/CD is one of the best things you can do to improve product quality.) To that end, Rainforest has a first-class API, CLI tooling, and a CircleCI Orb.