← Back to projects

Case study

Lantan

Fractional real estate. Real money. No room for regressions.

Lantan
My role
QA Engineer
Industry
PropTech / Fintech
Platform
Mobile (iOS & Android)
Year
2024

Overview

Lantan is a mobile investment platform that lets Nigerians co-own curated real estate in slots — earning annual rental yield and appreciation, with the ability to resell slots when they need liquidity. I owned QA for the mobile flows where every defect risked either a user's money or the platform's credibility.

What I owned

  • ◆Onboarding & NIN identity verification — including confirmation, error and retry states
  • ◆Property discovery, filtering, and detail screens with live investment data
  • ◆Buy-slot flow: amount entry, payment method, virtual account timer, receipt & email
  • ◆Resell flow: partial vs. full resell, confirmation, wallet credit
  • ◆Wallet: top-up, payouts, yield credits and transaction history
  • ◆Push and in-app notifications across the investment lifecycle

Approach

Money-flow risk model

Every screen was classified by financial impact. Anything that moved naira — invest, resell, top-up, payout — got exhaustive coverage including boundary values, network drops mid-transaction, and duplicate-submission attempts.

KYC & sensitive-data testing

Verified NIN capture, masked display, confirmation sheet, and the verified/unverified account state machine. Confirmed sensitive fields never leaked into logs, screenshots or analytics events.

Real-device coverage

Tested on a matrix of physical iOS and Android devices across OS versions, screen sizes and network conditions (WiFi, 4G, throttled) — because mid-transaction reality is not a simulator.

Regression & release readiness

Built a smoke pack for daily builds and a full regression pack for release candidates. Ran exploratory sessions each cycle focused on new features and their neighbouring flows.

Outcomes

  • ✓No production defects on the buy-slot or resell payment paths after launch
  • ✓Caught and reported timer-drift, receipt-mismatch and duplicate-payment edge cases pre-release
  • ✓Locked down KYC edge cases (retry, mismatch, expiry) before they reached real users
  • ✓Gave engineering a repeatable release checklist tied to real user journeys

Tools

JiraTestRailPostmanCharles ProxyXcode SimulatorAndroid StudioReal device lab