Case studies/GrowSari
How QApilot moved GrowSari from a regression plan to evidenced mobile automation on a real B2B commerce app: cloud-device login, Record & Playback through OTP-gated store-owner journeys, and team adoption that kept growing while app-side OTP fixes continued.
·
Results
About the project
GrowSari is a tech-enabled B2B platform for the Philippines' sari-sari stores: on-demand inventory, e-services such as load and bills payment, and working-capital tools in one app. Store owners depend on ordering, payments, Scan & Pay, and fulfilment every release. Those revenue journeys sit behind login, OTP, and MPIN gates, so automation only matters if it can survive real auth and run on real devices, not just document a regression plan. GrowSari website.
Impact
Before
With QApilot
Before
A regression plan and test cases existed, but the team still lacked reliable automated runs on the live GrowSari app.
With QApilot
Store-owner journeys were recorded in QApilot and re-run on cloud devices, with shared execution reports the team could use as release evidence.
Before
Login stalled automation: OTP timed out mid-run, keypad entry was brittle across devices, and security controls blocked unclean lab phones.
With QApilot
Cloud-device execution gave a clean login path, and element-aware Record & Playback handled OTP and MPIN entry without fragile coordinate taps.
Before
Pushing a crawl-everything first pass through OTP-gated commerce navigation produced unstable exploration and little usable coverage.
With QApilot
Record & Playback carried the auth-gated revenue flows first. The autonomous crawler and knowledge graph stayed available for broader discovery once those gates were under control.
Before
Enablement risked stalling while app-side OTP and environment issues were still open with GrowSari engineering.
With QApilot
Hands-on workshops still shipped Login, Scan & Pay, and Place Order (COD) coverage, and adoption kept rising while those app-side fixes continued.
Our approach
QApilot treated GrowSari as a release-readiness engagement on a real B2B commerce app: unlock authentication, automate the journeys that make money, and leave the team with runs they can repeat, not a slide deck about readiness.
01
The first constraint was getting into the app at all. Store-owner flows sit behind phone login, OTP, and MPIN. Lab-device security limits and short-lived OTPs were stopping runs before catalog, cart, or checkout coverage could start. QApilot moved execution onto cloud devices for a controllable login surface, then recorded auth with element-aware steps so OTP and MPIN entry stayed stable across layouts instead of breaking on pixel taps.
02
With login workable, the engagement used Record & Playback for the intentional revenue paths GrowSari already cared about: Login with OTP and MPIN, Scan & Pay, and Place Order with cash on delivery. That matches how QApilot is meant to be used: autonomous crawl and the knowledge graph for open discovery, Record & Playback when a team needs precise, human-defined coverage through gated commerce flows. Blockers that belonged in GrowSari's app or environment stayed with their engineers; platform work stayed on recording, execution, and reporting.
03
Enablement ran in parallel with those fixes. Feuji-partnered workshops walked the team through intake, recording, cloud execution, and reading reports so regression was no longer a planning artifact. Test steps grew +161% and active users +75% across checkpoints, including while OTP changes were still pending on the app side. The outcome was evidenced automation the GrowSari team could keep running after the workshops ended.
Engagement highlights
Cloud devices used for a clean store-owner login path past lab-phone security limits
OTP and MPIN recorded with element-aware steps instead of brittle coordinate taps
Login, Scan & Pay, and Place Order (COD) covered with Record & Playback
Autonomous crawler kept for broader discovery after auth-gated paths were stable
Shared cloud execution reports turned workshop runs into release evidence
Team adoption continued (+161% steps, +75% active users) while app-side OTP work stayed open
What QApilot delivered
Technologies and tools
QApilot moved GrowSari onto cloud devices and recorded phone login, OTP, and MPIN so automation could enter the app instead of failing at the gate.
Once auth worked, the engagement recorded the store-owner paths that matter for releases: login, Scan & Pay, and cash-on-delivery checkout.
Record & Playback carried precise, human-defined coverage through OTP-gated flows. The autonomous crawler and knowledge graph remained available for open exploration afterward.
Feuji-partnered workshops covered intake, recording, cloud execution, and reports so GrowSari left with repeatable regression, not a one-off lab demo.
Next
QApilot turned GrowSari's regression plan into measured mobile coverage by unblocking login on cloud devices, recording OTP-gated store-owner journeys with Record & Playback, and keeping adoption moving while app-side OTP work continued.
More stories
Wio
Reliable automation on a Flutter banking app, owned by a small QA team
Read the story
Geml
Full sanity automation for a pre-launch dating app, in two weeks
Read the story
Explore related capabilities
GrowSari needed to move from regression planning into evidenced automation on store-owner journeys. Cloud-device login and OTP-gated flows were blocking progress while app-side OTP work continued.
With login unblocked on cloud devices and Record & Playback on OTP-gated store-owner journeys, GrowSari reported +161% test steps and +75% active users while adoption kept moving during OTP work.
Record & Playback captured OTP-gated store-owner flows once login worked on cloud devices, so the team could grow coverage instead of waiting for every app-side OTP dependency to finish first.
Autonomous testing, CoWork, and dual-device testing — used together to turn a regression plan into measured mobile coverage on real store-owner journeys.
