mobile app testing

How Jitjatjo Scaled Mobile App Testing Coverage by Making QA Work Smarter

Picture of Ashley Dotterweich
Ashley Dotterweich, Wednesday July 5, 2017

Mobile app testing can be difficult for most mobile dev teams, and it can be especially challenging for teams that are growing rapidly. For Jitjatjo, maintaining a consistently high level of application quality is critical to the success of their online workforce marketplace, but limited in-house resources have constrained their ability to build out a traditional QA process.

Jitjatjo's Head of Product, Dominic Esposito, wanted to keep his development team as lean as possible without sacrificing product quality. Finding an efficient approach to testing was critical to achieving this balance. Here’s how Jitjatjo has used crowdsourced QA to build a scalable approach to mobile app testing for their lean team.

Use QA and Development Resources Carefully

Jitjatjo has a distributed development team, with a single QA engineer to support their application. Because testing resources are tight, Dominic has focused on building a strategic QA process that uses minimal internal resources for test execution. His goal is to keep his QA engineer focused improving the overall quality of the product, rather than continually executing functional tests.

Rainforest Mobile App Testing gives Jitjatjo access to a crowdsourced network of testers, allowing them to offload the majority of their repetitive tests from the internal team. By boosting capacity for functional and regression testing, Rainforest gives Jitjatjo’s QA engineer more time to focus on other forms of testing, from building out test cases to exploring new features.

Make QA a Priority as Early as Possible

Dominic’s team has shifted QA as early as possible in their development cycle. The initial test cases are drafted before any code is written, while new features are still being designed. After the code is ready, tests are edited to reflect any changes to how the feature functions. By starting QA as early as possible, the development team can focus on building a quality product from the start. “Rainforest has forced us to prioritize and invest in test case writing, which has made a huge impact on our development team,” says Dominic.

Test More with Less Effort

Device and OS fragmentation are major concerns for mobile app developers. Achieving the level of coverage needed for confident releases can require a huge amount of testing. Many teams end up maintaining massive numbers of test cases, which must be updated and added to continuously.

Jitjatjo has solved this issue by taking advantage of Rainforest’s embedded tests feature. Every test they write is entirely modular, reducing the overall need to write a new test script for every new feature or product update. As a result, Jitjatjo is able to update their test suite very quickly and execute tests more efficiently. “Rainforest allows us to create a test that we can run over and over. Any time we want to test that flow, we gain the efficiencies back,” Dominic says, “Any Rainforest test case that we write becomes extremely efficient. We’re saving 25-30% of our QA time by leveraging Rainforest.”

Read Jitjatjo’s Rainforest Case Study

Leveraging Rainforest has allowed Dominic’s team to scale up their mobile QA testing process without spending more time on test execution. To learn more about how Jitjatjo has implemented Rainforest, and to learn how other teams can achieve the same benefits from crowdsourced testing, check out our case study of Jitjatjo.

Filed under: jitjatjo, mobile app testing, and mobile qa