74%
of planned sprint automation delivered
Case studies/Wio
Complex mobile banking journeys, turned into scalable automation coverage
How QApilot helped Wio's automation team scale coverage across onboarding, credit applications, identity verification, biometric flows, API validations, and cross-OS execution.
- Digital banking
- Mobile-first
- Identity & biometrics
- Client
- WIO Bank
- Industry
- Digital Banking
- Platforms
- iOS, Android
Technologies and tools
- QApilot Recorder
- CoWork
- AI healing
- LambdaTest biometric bypass
- Face ID / fingerprint validation
- HTTP keywords
- Dynamic test data
- Cross-OS execution
Results
Results by the numbers
71%
of the Identity suite automated, including biometric-gated journeys
35%
of Retail flows automated in the first delivery wave
About the project
Here's a bit about Wio
- Industry
- Digital banking
- Headquarters
- Abu Dhabi, UAE
- Engagement
- Ongoing
- Platforms
- iOS, Android (Wio Personal and Wio Business)
Wio is a Central Bank of the UAE-licensed digital bank. Customers open Personal and Business accounts from the mobile app with Emirates ID or UAE visa verification, then save, spend, borrow, and invest in one place. Those same journeys, onboarding, identity, biometrics, credit applications, and API-backed checks, are exactly where record-and-playback tools stall. QApilot automated those release-critical mobile flows on the real banking app, not a simplified demo. Wio website.
Impact
Before and after QApilot
- 01
Before
Banking journeys that defeat record-and-playback: biometrics, identity, API-driven validation, dynamic test data, and cross-OS runs.
With QApilot
Structured automation across retail, SME, identity, onboarding, credit-application, and API-heavy flows.
- 02
Before
Squads still learning the platform, with little sprint coverage converting into reliable automated suites.
With QApilot
War-room support, daily syncs, and one-to-one enablement turned adoption into measurable sprint delivery.
- 03
Before
Failed and stopped runs on dynamic app behaviour, with little recovery once a step broke.
With QApilot
Step- and case-level conditions, assertions, if/else, recovery, exception blocks, and AI healing toward reliable completions.
- 04
Before
UI-only scenarios that could not represent Face ID, fingerprint, or API response reuse.
With QApilot
Biometric bypass, Face ID / fingerprint validation, HTTP keywords, random/API test data, and larger-APK cross-OS execution.
Our approach
Our engagement
QApilot joined as a product partner, not a dropped-in tool. The goal was measurable coverage on the journeys that matter for release: retail, SME, identity, onboarding, credit, and API-backed checks.
The first move was out of platform exploration and into structured delivery: retail, SME, identity, onboarding, credit-application, and API-heavy suites, tagged so each squad could see coverage land against their own journeys.
Stability work targeted dynamic behaviour. Conditions, assertions, recovery and fallback, exception blocks, and AI healing for XPath identification cut failed and stopped runs. Banking-specific execution followed: biometric auth bypass on LambdaTest, Face ID and fingerprint validation, HTTP keywords in Recorder, update-test-data during execution, and random data generation across API and RPA.
Results followed the same suites. Planned sprint automation reached 74%. Identity hit 71%, including biometric-gated journeys that generic tools never finished. Retail opened with 35% automated in the first delivery wave, with biometric, Face ID / fingerprint, and HTTP capabilities shipping mid-engagement so coverage could keep expanding on the real app.
Highlights
Engagement highlights
- 01
Biometric auth bypass, Face ID / fingerprint validation, and HTTP keywords shipped mid-engagement
- 02
Update test data during execution, random data generation, exception / execute-on-failure blocks
- 03
Extended scheduler window, AI healing for XPath, reset-app keyword, step cloning
- 04
Import and create functional blocks in Recorder, squad-tag and user-wise filtering, larger-APK execution
- 05
Forward-deployed RCA on failed runs, XPath guidance, onboarding-flow setup, and CoWork enablement
- 06
Alignment sessions that bridged documented test cases with actual app behaviour
What QApilot delivered
What QApilot shipped
01
Faster coverage across complex flows
Moved from platform exploration to structured automation delivery across retail, SME, identity, onboarding, credit-application, and API-heavy journeys.
- Squad-tagged suites
- Sprint-level coverage delivered
- Release-critical journey focus
02
Stability for dynamic app behaviour
Step- and case-level conditions, assertions, if/else, recovery, exception blocks, and AI healing so runs complete instead of stopping on the first mismatch.
- AI healing for XPath identification
- Exception / execute-on-failure blocks
- Reusable functional blocks
03
Banking-specific execution
Biometric bypass, Face ID / fingerprint validation, API response reuse, dynamic and random test data, and cross-OS support beyond UI-only scenarios.
- LambdaTest biometric bypass
- HTTP keyword in Recorder
- Larger-APK and cross-OS runs
04
Forward-deployed engineering
War-room support during ramp-up, daily syncs, RCA, CoWork enablement on recording, execution, reporting, and test-case management.
- One-to-one enablement
- Documented-vs-actual flow alignment
- Onboarding-flow setup
Facing similar challenges to Wio?
Record-and-playback tools stall on biometrics, identity, and API-driven banking flows. QApilot automated them, shipped banking-specific capabilities mid-engagement, and left Wio with measurable coverage on the journeys that matter for release.
Explore related capabilities: Autonomous testing, AI self-healing, CoWork, Enterprise.