Mike Bennett

Case study

Fintech · Regulated — Launch phase

QA for a regulated fintech platform under launch pressure

A regulated online investment platform needed test infrastructure and a defect process that would hold up under compliance scrutiny, without slowing delivery.

3

platforms validated

2

third-party APIs integrated

1

QA process built from scratch

Context

Regulated investment products carry consequences that ordinary web defects do not: money movement, investor eligibility and disclosure flows all have to be exactly right.

Risk

The failure modes that mattered lived in third-party integrations the team did not control, and in flows where a wrong state is a compliance event rather than a bug.

Approach

  1. Established the QA process and test infrastructure from scratch on a product already moving at launch pace.
  2. Combined exploratory testing on the high-consequence money and eligibility flows with targeted scripted checks in Cypress, Python and PyTest.
  3. Validated third-party financial APIs and the Salesforce API across desktop, iOS and Android clients.
  4. Ran the defect lifecycle end to end in Jira, Zephyr and Confluence with national and offshore teams.
  5. Reported status in terms of business risk so non-technical stakeholders could make an informed go or no-go call.

Result

The platform shipped on desktop and mobile, and went on to support successful crowdfunding rounds for real companies and investors.

Evidence

Delivered a test plan, defect lifecycle in Jira and Zephyr, Confluence documentation, third-party integration test coverage and business-risk status reporting for go or no-go decisions.

Stack

  • Cypress
  • Python
  • PyTest
  • Jira
  • Zephyr
  • Confluence
  • REST APIs
  • React
  • Javascript
  • MySQL
  • Swagger