“Instead of having someone to manually go in and triage what’s failing, using Rainforest helps us save about an hour every day for the automation team.”
- CareCloud’s manual QA team saves 180 hours/sprint on repetitive testing with Rainforest QA
- CareCloud streamlined their test automation workflow by using Rainforest tests as a template for automated test scripts
- CareCloud uses Rainforest “Automation Fallback” to ensure every feature continuous test coverage
Test automation and manual testing each have their own benefits to teams looking to ensure that they ship the highest quality software. CareCloud’s QA team takes a hybrid approach to their testing strategy to gain both the speed of automation and the flexibility of manual QA.
Maintaining a High Bar for Software Quality
CareCloud’s development team builds and maintains a range of cloud-based web applications for the healthcare industry, from EHR software to medical building management tools. Their customers have high expectations for product quality, but the complexity of CareCloud applications leads to an inherent risk of new bugs every time the team ships a new or updated feature.
To ensure that the quality of CareCloud’s suite of products meets their high standards, CareCloud has both a manual testing and a testing automation team in-house. The teams collaborate closely, and use Rainforest as part of their mutual workflow to streamline test execution and automation.
Accelerating Manual Test Execution Cycles
QA Engineer Ryan von Rosenberg leads the implementation of Rainforest for CareCloud on the manual testing team, which is largely responsible for finding new bugs and improving the user experience. Ryan’s team uses Rainforest to optimize test execution, which has reduced their functional testing ahead of releases from a full week of manual happy path testing to a 30-minute run of their Rainforest suite and a day and a half of manual edge case checking per sprint.
As new features prepare for launch and potential regressions are discovered, test cases are added into Rainforest. Maintaining a test suite in Rainforest lets the CareCloud team quickly execute and re-execute test cases during staging and early production, freeing up the manual testing team to focus on finding unknown issues and work with the developers on UX improvements.
Streamlining Test Automation with Rainforest Tests
With a large and continually growing test database, CareCloud also uses test automation to ensure that stable features have appropriate test coverage. The automation team leverages Rainforest tests as an essential part of their workflow for scripting automated tests.
“Having the Rainforest test run green before they hand it off to the automation team ensures that anyone on the team can come in and run the test. It’s a verification that the issue is reproducible.”
Rainforest provides automation engineers with context on the feature needed to script tests effectively, as well as the confidence that each test case has been verified by humans before it reaches their team. This information reduces the time required for the automation team to interpret manual test scripts and determine whether a feature is stable enough for automation. “Having the Rainforest test run green before they hand it off to the automation team ensures that anyone on the team can come in and run the test. It’s a verification that the issue is reproducible,” says Zachory Strike, who leads the test automation team at CareCloud.
Improving Bug Triage Workflow
“Getting to the confidence that something is failing as fast as possible is key,” Zachory says. “If a test fails in automation and we kick it off as a Rainforest test, we can be pretty confident that it’s not our automated test that’s broken, but an actual bug. If the automated test fails but the Rainforest test passes, we know that we probably need to refactor the automated test.”
“If a test fails in automation and we kick it off as a Rainforest test, we can be pretty confident that it’s not our automated test that’s broken, but an actual bug.”
Rainforest provides CareCloud with a “safety net” against any issue with automation test cases. Every automated script is paired with a Rainforest test script. Therefore, if an automated test fails, the Rainforest test case is immediately triggered. This frees up the time the automation team would have spent validating whether the failure was a result of a broken automation script or a real bug. “Instead of having someone to manually go in and triage what’s failing, using Rainforest helps us save about an hour every day for the automation team,” says Zachory.
Additionally, if an automated test breaks, the team can easily revert to the Rainforest test until the team has time to update the automation script, ensuring that a brittle automated test doesn’t impact QA coverage for any given test run.
Learn More about How CareCloud Uses Rainforest QA
Rainforest has streamlined CareCloud’s QA workflow and helped both manual QA and automation engineers to recover hours from test maintenance and execution every week.
To learn more about how CareCloud’s manual testing team uses Rainforest QA to streamline their workflow, read our interview with Ryan on “What QA Teams Need to Know about Rainforest.”