Challenge
Flex Funding was moving its financial platform's frontend from Nuxt 2 to Nuxt 4, largely with AI tools. The speed of the migration called for independent control: the app serves investors, borrowers, documents and payments, so any regression in core journeys is a real business risk. The client also wanted to avoid old-school full manual QA.
Scope
- Build health: production build succeeds, no critical console or runtime errors in staging
- Core journeys: E2E coverage for sign-in, onboarding/KYC entry points, investor flow, borrower loan application, document upload/download, payments/subscriptions, back-office approvals and notifications
- Route coverage: every major route loads and renders correctly, including guarded pages and error states
- Data integrity: API calls, async loading states, calculations, tables, pagination, filters and status transitions
- Compatibility: third-party modules and plugins verified as compatible or replaced
- Short exploratory testing only on high-risk flows and edge cases
- Handover: migration notes, unresolved issues and architecture changes
Solution
We based migration sign-off on objective criteria rather than clicking through the whole app by hand: build and type-check in the pipeline, automated E2E tests of core business journeys, checks of every major route and of data correctness, and finally a short, targeted exploratory session where the risk is highest. The code review covered components, plugins, authentication, routing and pipeline configuration, among others.
Technologies
Outcome
The client got a migration assessed against clear, measurable criteria, automated tests of core journeys that stay in the project for future releases, and handover documentation listing open issues and architecture changes — without costly full manual QA.