Scaling QA as a Strategic Function for a High-Growth Fintech Platform

‍

Background & Challenge

• Rapid Feature Velocity: Payment, transfer, and KYC features were shipping weekly, and the QA function needed an automation-first model to match that cadence as the platform scaled.
• Regulated Financial Flows: Payments, transfers, account operations, and KYC verification required deeper end-to-end coverage to support the regulatory environment the platform operates in.
• Growing Engineering Organization: With more squads shipping in parallel, QA needed to scale through tooling and process rather than headcount alone.
• Unified Test Asset Management: Test cases lived across multiple surfaces, and the team wanted a single, traceable source of truth linking requirements, cases, and runs.
• Connecting Test Signals to Production Health: Test results and production monitoring were tracked separately, and the team wanted a closed-loop view of release quality post-deploy.
• Scalable Execution Infrastructure: As the suite grew, the team needed an execution model that scaled horizontally rather than linearly with test count.

How We Helped

Strategic Repositioning of QA Across the SDLC

• Embedded QA across refinement, design reviews, sprint planning, and release decisions, so quality input shaped features from the start rather than at the end.
• Co-authored acceptance criteria with Product, with QA owning the testability lens, resolving ambiguity before code was written.
• Established QA presence early enough in the cycle to prevent defects rather than catch them after the fact.

Centralized Test Case Management in Testmo

• Consolidated test assets into a single Testmo repository with clear ownership per domain (payments, transfers, KYC, accounts).
• Linked every test case to its originating requirement and to the automated test executing it, giving traceability from requirement to case to run to result.
• Wired Testmo into CI/CD so every pipeline run posted automated results back into the corresponding test plan, replacing manual entry.

End-to-End API Automation Foundation

• Built a comprehensive E2E API test layer in Postman with Newman, covering payment, settlement, refund, transfer, account lifecycle, and KYC verification flows.
• Established API-level automation as the backbone of the strategy - validating backend correctness independently of the UI and giving fast feedback before any UI tests ran.
• Modeled tests around real financial scenarios rather than endpoint smoke checks.

UI & Integration Testing with Playwright

• Built UI and integration suites in Playwright covering critical web flows - onboarding, KYC submission, payments, transfers, account history - running against the real backend with seeded test data.
• Combined UI assertions with backend state checks in the same test, validating that what the user saw matched what the system recorded.
• Reserved mocks for edge cases only - third-party provider failures, timeouts - while keeping core money flows tested against real backend behavior to avoid mock drift.

Cloud-Native Execution on AWS Lambda and S3

• Designed a distributed execution model on AWS Lambda - Postman/Newman runs and Playwright shards triggered as Lambda invocations, scaling horizontally with the suite.
• Stored all test artifacts - logs, traces, screenshots, videos, JUnit reports, Newman exports - in S3 with lifecycle policies, giving a durable record of every run.
• Kept suite execution time stable as coverage grew, supporting faster release cadence as the business scaled.

Production-Grade Observability with New Relic

• Instrumented the test execution layer with New Relic, making test runs, flakiness, duration trends, and failure clusters first-class telemetry rather than buried CI logs.
• Correlated post-release production metrics with the most recent test runs that covered the affected flow, closing the loop between "tests passed" and "production is healthy."
• Gave Engineering, QA, and PM a shared operational picture of quality and release health.

Outcomes & Benefits

• QA as a Strategic Bridge: Embedding QA across refinement, design, and release decisions positioned the function as the connective tissue between Engineering, Product, and the business.
• Single Source of Truth for Coverage: Testmo gave the team a centralized, traceable repository where every requirement, case, and run was linked, making coverage visible across squads.
• Comprehensive E2E Coverage on Money Flows: Postman and Playwright together covered the regulated, high-risk paths - payments, transfers, KYC, account lifecycle - with both API-level and UI-level validation.
• Stable Tests Without Mock Drift: Real backend with seeded data for core flows and mocks only for edge cases kept suites stable while staying faithful to real production behavior.
• Execution That Scaled With the Business: The AWS Lambda and S3 execution layer scaled horizontally with the suite, so feedback got faster as coverage grew.
• Closed Loop Between Tests and Production: New Relic correlation between test runs and production health gave the team a shared, real-time view of release quality.

Tech Stack

• Playwright - end-to-end UI and integration testing
• Postman / Newman - API automation
• Testmo - test case management, traceability, and reporting
• New Relic - test run observability and production health correlation
• AWS Lambda - distributed, on-demand test execution
• AWS S3 - test artifact storage
• GitHub Actions - CI/CD orchestration
• TypeScript, Python, Node.js

‍