FacebookGlassdoor Social IconInstagramLinkedInTwitterYouTubeFacebookGlassdoor Social IconInstagramLinkedInTwitterYouTube
skip to Main Content

“Every solution has their pluses and minuses, but ultimately Rainforest is the best long-term fit for us. As we grow the development team, we can easily scale testing to support the amount of effort the developers are putting forth.”

Download Case Study

  • Expanded test coverage from 0% to 80% for new UI in about 1 week
  • Reduced testing cycles from 1 week to 3 days
  • Increasing deployment cadence from 1x monthly to 2x monthly

Leveraging Rainforest Test Writing for Quality Coverage and Scalable QA

Finding the right amount of test coverage is a common challenge for many development teams, especially as their product changes. In order to keep coverage high without creating a cumbersome QA process, RhinoDox turned to Rainforest for a fast, scalable approach to QA.

Finding an Alternative to Selenium Automation

RhinoDox, an enterprise content management platform, started out with a single quality engineer writing Selenium scripts for their product. This proved to be an excess of coverage for them, and they decided that they didn’t have enough testing automation needs to justify the cost of a full-time QE.

To fill the gap in their regression testing, RhinoDox switched to using an outsourced QA manager. However, this siloed QA execution with a 3rd party and slowed down their release cycle for every launch. RhinoDox’s primary goal was to reintroduce regression testing to catch known issues. They also wanted to ensure their app had sufficient test coverage to discover unknown bugs before they impacted users.

Using Rainforest Test Writing to Kickstart Coverage

RhinoDox implemented Rainforest as an alternative to their existing Selenium test suite. At the time they were developing a brand-new frontend. With consultation from Jeff Pineda, QA Professional Services Expert for Rainforest, and the Rainforest test writing engine, RhinoDox was able to kickstart their test coverage for the new UI. RhinoDox went from no coverage to a comprehensive functional test suite — about 80% of the test cases they ultimately needed — in about a week.

Using Rainforest to build the test suite provided the added benefit of being able to quickly create tests optimized for execution on the Rainforest platform. Jeff was able to employ advanced Rainforest test writing features, such as embedded tests for common flows, rapidly and effectively.

Faster Testing Leads to Faster Deployment Cycles

Rainforest has allowed RhinoDox to speed up the testing process, bringing the entire QA cycle for each release down from a full week to a few days. Travis Whelan, Principal Engineer for RhinoDox, explains: “Before Rainforest our developers were throwing things over the wall to our QA person. He required about a week of time to run a full regression set. Now we run a full regression set in Rainforest and we have results in 30 minutes.”

Travis notes that streamlining QA has allowed RhinoDox to think about how they can speed up their deployment process overall. “We’re looking to shorten our release cycles even further. Right now we release once a month, and we’re planning to move that to once every two weeks. Rainforest allows us to do that without making a large investment in a team of human testers.”

A Scalable, Sustainable QA Process

Rainforest gives RhinoDox a more streamlined software testing flow. Developers write code and unit tests, then perform code reviews. The Rainforest QA platform executes a regression testing suite to check for any issues.

Since Rainforest built out an initial test suite for RhinoDox, optimizing for the coverage they needed most, managing and maintaining their test suite has been relatively simple. “Because we have a pretty solid set of tests already, it’s easier to evolve and add on to our test suite as we add functionality,” says Travis. This continuous coverage lets Travis’ team keep a pulse on whether things are breaking, especially in their legacy application, which can be impacted by new releases but is not the focal point for developers.

Eventually, the RhinoDox team plans to have developers write Rainforest tests alongside code to bring QA even closer to development. By leveraging Rainforest, RhinoDox is able to plan for the growth of their development team and product more effectively: “Every solution has their pluses and minuses, but ultimately Rainforest is the best long-term fit for us. As we grow the development team, we can easily scale testing to support the amount of effort the developers are putting forth.”

Name RhinoDox
URL www.rhinodox.com
Industry Document Management
HQ Chicago, IL
Employees 11-50
Founded 2016