
80% fewer bugs in a U.S. healthcare product
A scalable QA process for a healthcare product with several user roles, mobile apps and patient data.
80% fewer bugs- 80% fewer bugs
- 320+ bugs reported, 28 critical
- 2× faster release cycle
- Platformsweb, iOS, Android, API, admin dashboard
- Engagement12 months · 4 QA engineers
The product was growing fast, but testing was done by developers before each release, with no test plans or regression suite. Bugs regularly reached production, and patient-data access rules were never tested systematically.
We built a QA process from scratch: test plans, regression suites and release checklists for every user role. We tested web, API and mobile apps on real devices, including GPS and check-in flows, and added access-control checks against OWASP Top 10 and accessibility checks against WCAG 2.1 AA.
Bugs dropped by 80%. Releases moved from a four-week to a two-week cycle, and production errors are now reviewed after each release and turned into regression tests.
- Weeks 1–3
Product study, test strategy, first regression pass
- Weeks 4–12
Test cases for all roles, API and mobile coverage
- Weeks 13–30
Automation of 180 key scenarios, CI integration
- Weeks 31–52
Security and accessibility checks, release-by-release support
Tools
-
Playwright
- Postman
- Appium
-
BrowserStack - Jira
- TestRail
- Charles Proxy
-
axe DevTools - Datadog
- Sentry
- Firebase Crashlytics
-
AWS CloudWatch
Testing types
Want results like these?
Book a short call about your product. We can start with a free QA audit or a trial.