
I like the fact that the test case writing process is as simple as your understanding for the feature you are writing for. By having the english step by step option, test case writing looks more like a story that the crowd tester is integrated with than just a dumb terminal running a test case suite. Also the feedback from the crowd makes it easy to troubleshoot the issue or add more clear and concise verbiage to the existing test case. Lastly,I like it that Rainforest has decided to bolster their initiative to make the automation testing more robust. I look forward to harness the potential power of such a testing tool. Review collected by and hosted on G2.com.
I dislike the amount of time that it takes to spin up a virtual machine instance for the English written cases as well as the automation cases. There are times when I have waited several minutes for the terminal to be ready. In our world that seems like a lifetime. I also am not fond of the amount of time that it takes for the automation to cache and run the test cases after the vm has loaded. It does not appear to front load the cases and then run them instead it appears that it reads each test case in serial prior to loading and then running. I am also not a fan of not having some sought of library that can be used when creating the automation cases. Lastly, there should be an auto save for the automation case writing so that you don't lose hours of work because somehow the window got closed or navigated away from. Review collected by and hosted on G2.com.
Great selection of browsers, browser VM's work even better than Browserstack for emulation. Review collected by and hosted on G2.com.
There have been many false positives from a variety of sources. Language barriers and just straight up tester error. It would be nice to have multiple options before declaring a failure. "Did A happen? If yes, move to next step. If no, check for B. Did B happen? If yes, move to next step. If no, mark as failure." Delays between kicking off tests and getting feedback can sometimes make it impractical for continuous deployment cycles. Scrolling within the VM and even the VM's screen display is not optimized for smaller device screens. Review collected by and hosted on G2.com.
Relationship
Mouse tracking of the actions as part of the tests
Consistency of the test (automation-like) with visual validation Review collected by and hosted on G2.com.
Well, we always want everything to be cheaper... Review collected by and hosted on G2.com.
The ability to call it from CI tools, the way to create the tests and the fast run times. Review collected by and hosted on G2.com.
The UI is sometimes a bit cumbersome to use. It's hard to run changed tests in a bundle, without creating a lot of tabs Review collected by and hosted on G2.com.
Integration with external service i. slack enable monitoring of the status of the tests without necessarily logging into the application
also, the test run really fast..faster that the earlier E2E system we had before Review collected by and hosted on G2.com.
It would be awesome to allow importing of test from an external VCS i.e Github as it would make it easy to have internal review of tests between the development team. Also this will allow version of the tests per the application Review collected by and hosted on G2.com.
I can get a full QA run done quickly, at any hour of the day Review collected by and hosted on G2.com.
Tests have to be written in a very specific way. Testers follow instructions to the letter and won't make any assumptions or logical leaps, even when you think it should be obvious. This produces very predictable results, but it also means writing tests that produce a passing result can require a fair amount of trial and error. Review collected by and hosted on G2.com.
-Feedback speed: hundreds of test steps executed within an hour
-Reliable results: every test case is executed by multiple testers, most of the false results are filtered out by Rainforest automatically
-Low maintenance costs Review collected by and hosted on G2.com.
The initial effort for creating test cases is high. Review collected by and hosted on G2.com.
The ability to update, edit and maintain your test scripts are my absolute favorite. Well then there's the amount of testers they have is another great feature! Review collected by and hosted on G2.com.
We had one technical issue that caused all of our test to fail but that was quickly resolved by the support team. Review collected by and hosted on G2.com.
Using Rainforest QA has saved my team numerous hours in regression testing before a big deployment! I love it! Review collected by and hosted on G2.com.
There is not too much I do not like. I found the on-boarding and customer service exceptional. The account manager assigned to our account has been a pleasure to work with and is very responsive. Review collected by and hosted on G2.com.
When dealing with an unpredictable UI (developing on top of partner websites), it can be really hard to write automated e2e tests. Rainforest QA alleviates these concerns and lets you dictate instructions instead of trying to codify edge cases. Review collected by and hosted on G2.com.
The QA tests occasionally will get tripped up, even when given specific instructions. Review collected by and hosted on G2.com.
I like the simplicity of the UI, the browser options available and the variables system. The amount of information on the tests being run is also valuable. Support and our account manager have always been a pleasure to interact with and I have always gotten timely responses. Review collected by and hosted on G2.com.
Organization options are limited for the tests page. I would like more options for organizing folders. Also the tests results page has limited options for sorting or searching for specific sets of tests being run. Review collected by and hosted on G2.com.
- Easy to write Tests and embed steps
- Easy to Review Results
- Easy to Verify Failures with mostly clear explanation given my the testers around the world and with the help of the screenshots displayed on every step.
- Sorted Cross browser Testing
- There are new mobile platform coverage which we have not tried it.
- Client Support is quick to respond
- Prevent bugs from getting to the production environment Review collected by and hosted on G2.com.
- Getting to know the workflow at the beginning can take a while.
- Investment of time in setting up random login variables for testers
- Record n Play testers testing behavior would have been better than the screenshots but Rainforest has been working on it , so hopefully this wont be a limitation anymore
- The VMs are sometimes slow which causes false test failures as testers are not able to complete their tests.
- Cannot select a specific location testers to execute the tests
- Maintaining the tests could be a trouble Review collected by and hosted on G2.com.
1) Speed of results: we run our extensive regression test suite in as little as 30 minutes. This used to take 2 person weeks.
2) Maintainability: Rainforest QA makes our large regression test suite easy to maintain. Writing new tests for our latest development sprint or modifying exisiting tests in case of an application refactoring is just changing the text in a few places. Review collected by and hosted on G2.com.
1) The cost is significant. We currently run a regression test after each 2-week development sprint, and that is all we can afford. We would love to move towards more continuous delivery and continuous testing but that would break our budget.
2) Contracts are a bit inflexible Review collected by and hosted on G2.com.
Three or more testers can run tests in parallel. Tests can be executed round the clock. Test runs can be scheduled. Review collected by and hosted on G2.com.
When testers doesn't follow instructions or doesn't provide sufficient feedback Review collected by and hosted on G2.com.