Rainforest QA Reviews

Simple mental model and sleek interface.

Not much to complain about................

Lack of QA personnel.

Rainforest has revolutionised the way we do testing in the organisation. It is now regular, accurate and efficient and helps us quickly identify whether feature updates work as expected.

There really are hardly any - I haven't worked out how to trigger multiple test runs in one go yet, though I'm sure this will be possible.

Testing of some our features is often slow and requires a lot of human input as they include 100+ item surveys. The automation of Rainforest has saved us hours of time.

Ease of use is exceptional. Very easy to construct new test cases, as the application grows and changes, test cases are easy to change and update. Everything is visual and easy to understand, high marks for everything.

Would be good if test cases could be layered, for example on the success of creating an order, then searching for that order. In more complex systems such as insurance, this is an absolute requirement.

Providing a platform to test our application. This is all we use and it is excellent (other than layering test, which we achieve through the CLI and waiting (not very efficient)).

Creating tests is boring, but not with Rainforest! The interface is super-easy to use; click and take snapshots in your browser of choice. There are plenty of scheduling options.

My #1 favorite feature is supporting temporary email inboxes, os we can test the complete signup workflow of our SaaS!

Mobile-browser tests are preformed manually by QA people (so execution time is slightly slower, not ideal to be integrated in CI/CD).

Making sure that the critical features and workflows in our SaaS work, so we can sleep well :)

We use automated tests via Rainforest QA to replace the need of a full-time QA Engineer in our team.

The best thing about Rainforest is how easy it is to use. We are looking to have less technical team members create and maintain the Rainforest tests so that we can save a ton of time from the engineering side of things.

Right now since it has to reach out to a public facing website we are not able to run tests on our local environments while developing. It would be great if we could use it to automate some QA during development as well.

Rainforest is helping us ship code with more confidence. We use it to test our main app flows so that we can save time and be more confident that there are no regressions when we push out new features. This causes fewer bugs for our users or we are able to catch the bugs much more quickly and address them before any users see them.

I love how easy it is to create tests. Being able to create embedded steps and copy selected steps enhance the speed and which I am able to create tests. Plus, the comment step makes it easy to document the tests. Unlike other automation tools, I like that Rainforest relies on screenshots as opposed to classes & IDs to find elements, so it's as if an actual user is clicking through the steps.

Also, my experience with customer service at Rainforest is really good! I've raised a few questions/concerns over the last couple of years, and even if they can't be answered straight away, it's nice to have some acknowledgment, and then if I chase it's nice to know that it's not just been brushed aside, I always feel like it's in hand.

The only issue I can see these days, and it's not the biggest issue, but still, it would be good to address, is that the wait time is different between running a test in edit mode vs running a real test run; and I'm going to guess its because edit mode is running a single test and a real test run is running multiple tests at the same time, hence the slowness.

I work with a dev team of about 25-ish people in squads of about 5-6, which include 1 QA per squad. We try to release code changes daily, and having Rainforest means we don't have to worry about code changes breaking other system areas. We can test the tickets manually and then run the Rainforest testing suite to see if anything dodgy has occurred in other areas of the system. It's so easy to review the results, assign them to colleagues to fix/sign-off, and catagorise any failing tests; before requesting a code cut.

Rainforest is so easy to use and intuitive anyone can pick it up almost instantly. QA engineers, frontend engineers, and even backend engineers, but also product people can see exactly what is being tested, what breaks, and make updates in minutes. It also lets us test things that no other tool can test, by being truly "from the outside" in a browser in a VM.

Nothing really. The tool is great, the team is awesome and makes improvements to it constantly, and it keeps getting better. The only way Rainforest could be better is if it could fix my code for me.

We use Rainforest to test all the critical paths of our app, and move with confidence. Many times it has alerted to some regression and allowed us to fix things before they reach our customers.

It doesn't require extensive knowledge of code to build custom tests.

There's a slight learning curve, but this is expected for any auditing tool.

It made it easy to set up tests for our company's high priority landing pages, so that we can catch when things crash in the moment

One of the features I found most helpful was creating tests with randomized data. It was just what I needed as we were testing a new web app. The different fields it gave as options was really helpful.

I didn't like how it handles dynamic data. For instance, if you have a list view which keeps updating, it's almost impossible to test since you can't create an image of a dynamic list view

We recently moved from a desktop app to a web app. With our users, we needed to do a lot of testing to reduce customer complaints and foresee any issues we may not be able to test for.

How easy it is to learn the platform and get up and running. I was able to train our new QA testers and they were creating tests less than 15 minutes later.

I'm not sure if I have any negative feedback to share. My opinion is that the platform does 1 thing and does it well.

Our product has a lot of features and with every production deployment, all of those features have to be tested. So Rainforest QA allows us to establish a baseline and test the base features quickly.