Quality from the Ground Up for a Virtual Healthcare Benefits Platform

Plexteq established a full-spectrum QA practice for a US-based virtual healthcare benefits provider - cutting release cycles from quarterly to weekly and eliminating recurring regression failures across a PHP web application and Flutter mobile app.

Key Challenges

1. Uncontrolled regression across core member flows. Every release introduced a fresh wave of regression defects in the product's most critical paths - benefit eligibility checks, virtual physician session launch, prescription savings lookups, and mental health plan enrollment. With no automated safety net, breakages only surfaced after code had already reached production.
2. No test management or requirements traceability. There was no test management system, no structured test cases, and no traceability between business requirements and what had actually been verified. Testing was ad hoc and undocumented, making it impossible to know what was covered, what was at risk, or why the same issues kept coming back.
3. 90-day release cycle driven by fear, not process. The team was releasing once every three months - not because the product required it, but because the lack of a structured quality gate made every deployment a high-risk event. Business stakeholders were unable to ship improvements at a pace that matched market demand.
4. HIPAA compliance with no QA framework to back it up. As a platform handling electronic protected health information (ePHI) - the product was subject to HIPAA's Security and Privacy Rules. Yet there was no QA framework in place to validate that ePHI was handled correctly across access controls, data transmission, audit logging, or third-party integration boundaries. Compliance was assumed rather than verified, creating significant regulatory and business risk.

Plexteq approached the engagement as a quality transformation, not a quick fix. Rather than layering automation on top of an undefined process, the team started with a foundational audit and built the QA practice systematically - from strategy through to automation - in a deliberate sequence that allowed value to be delivered at every phase.

Phase 1. Discovery & strategy 

Plexteq's QA leads conducted a full analysis of the existing application features across both the PHP web platform and the Flutter mobile app. Every functional area was inventoried and mapped. A requirements traceability matrix was established to ensure that every testable requirement had explicit test coverage. Given the platform's obligation to maintain HIPAA compliance as a handler of ePHI, the QA strategy incorporated compliance-oriented test dimensions from the outset - covering access control verification, ePHI data handling across integration boundaries, audit logging behaviour, and data transmission security. This was formalised within ISO/IEC 25010:2011 framework, covering functional suitability, reliability, usability, security, and compatibility.

Phase 2. Infrastructure

Plexteq established a structured three-tier infrastructure - development, staging, and production - each with isolated data and consistent configuration. A blue-green deployment strategy was introduced, allowing the team to run two identical production environments in parallel. This made rollbacks instantaneous, eliminating the all-or-nothing risk that had previously made every release a high-stakes event.

Phase 3. Test Management

T​estRail was introduced as the central test management platform, giving the team a single source of truth for test cases, test plans, and run history. A sanity test suite was defined as a fast-pass gate to validate build stability before proceeding to full regression, becoming the practical enabler of shorter release cycles.

Phase 4. Automation

With a stable manual baseline in place, Plexteq implemented an automation strategy. End-to-end regression tests were built with Playwright, covering critical member-facing journeys across the web application - benefit eligibility flows, virtual care session launch, and plan management. Playwright's cross-browser reliability and strong async support made it a natural fit for an application with multiple embedded third-party service touchpoints. 

Measurable outcome

1. 12x More frequent releases - from quarterly to weekly production deployments
2. Zero Recurring incidents after the quality process was fully operational
3. <1 hr Rollback time in the event of a failed deployment, down from hours of manual recovery
4. 100% Critical journeys covered by structured test cases and automated regression runs