The Hidden Engine: How QA Powered the Driver App Transformation
Article Summary
Mohomed Nawab reveals how QA became the unsung hero in PickMe's driver app overhaul. Most teams treat testing as a final checkpoint, but this approach flipped the script entirely.
PickMe, Sri Lanka's leading ride-hailing platform, rebuilt their driver app from the ground up to address performance issues, GPS problems, and add in-app navigation. The QA lead shares the structured testing strategy that ensured thousands of drivers got a reliable tool for their daily income.
Key Takeaways
- QA joined from day one during planning and design, not just at testing phase
- Staged rollout: internal QA, beta drivers, then gradual production release minimized disruption
- Real-world road testing caught GPS and navigation issues lab testing missed
- Full regression cycle scheduled at project end instead of every sprint saved time
- Combined Appium automation with manual testing across device ranges and edge cases
Early QA involvement and real-world testing proved critical to delivering a stable driver app that directly impacts livelihoods and platform trust.
About This Article
PickMe's driver app had accumulated technical debt and UX problems. Drivers reported performance issues, GPS problems, and difficulties with a new in-app map feature that needed deeper mapping SDK integration.
Mohomed Nawab's QA team built modular functional tests covering positive and negative scenarios. They used state-based testing to check online and offline behavior, validated edge cases in location flows, and ran API tests with Postman and UI regression tests with Appium.
The structured QA approach allowed them to roll out changes in stages: internal QA first, then beta drivers, then gradual production release. This reduced last-minute bugs and the risk of widespread outages while keeping the app reliable for thousands of drivers who depend on it for daily income.