Mobile testing for React Native

Most React Native teams skip e2e tests.
Until the first production crash.

We set up Maestro end-to-end tests for your React Native app — YAML flows, CI integration, team handoff — in two weeks, one flat fee.

flows/login.yaml
appId: com.acme.app
---
- launchApp
- tapOn: Sign in
- tapOn:
 id: "email-input"
- inputText: "dev@weshipit.today"
- tapOn: Continue
- assertVisible: Welcome back
Why Maestro

A simpler stack for mobile tests

Most React Native teams skip mobile end-to-end tests or wrestle with Detox flakiness for months. Maestro takes a different approach.

Readable flows

A login test is 10 lines of YAML — readable by product managers, not just engineers.

Stable by default

Built-in retry and wait logic means you stop chasing flaky tests at 2am.

One flow, two platforms

The same script runs on iOS and Android. No duplicated test code.

Cloud-ready

Runs locally, in GitHub Actions, or on Maestro Cloud — you pick.

Open source

No vendor lock-in. Your tests are YAML files in your repo.

What you get

A productized engagement

Fixed scope, fixed timeline. Two weeks from kickoff to handoff.

Maestro installed and wired

Wired to your existing React Native project — iOS and Android, simulator and device.

5 critical user journeys

Login, onboarding, payment, core feature — picked with you during kickoff.

CI/CD integration

GitHub Actions workflow that runs your flows on every PR, or Maestro Cloud if you prefer.

Runbook & README

Tailored to your team — how to add a flow, debug a failure, run locally.

Recorded handoff session

30-minute session recorded so your team can refer back whenever.

14 days of follow-up

Direct message me whenever a flow needs adjusting after handoff.

Timeline

How the two weeks go

01
Week 1

Kickoff & setup

60-minute call to pick the 5 user journeys. We install Maestro, write the first flows, run them green on your simulator.

02
Week 2

CI & handoff

The remaining flows go in, GitHub Actions (or Maestro Cloud) is wired, runbook is written, and we record the handoff session.

03
After handoff

Follow-up support

Two weeks of message-based support so your team can ship flow #6 without rebuilding the setup from scratch.

Fit check

Who this is for

Good fit

  • React Native apps already in production (or close to it) with no end-to-end coverage today.
  • Teams burned by Detox flakiness who want a simpler stack.
  • Founders and CTOs who need confidence to ship faster without a dedicated QA hire.

Not the right fit

  • Apps still pre-MVP — wait until your core flows are stable.
  • Test stack already humming. We don't fix what isn't broken.
  • Exhaustive coverage (50+ flows, regression suites) — book a call for a custom scope.
Recent work

Real before / after

Maxence Cottel

QA engineer · Nacon

Mobile + e-commerce

Before

  • 0 end-to-end tests
  • 3h+ of manual QA per release
  • Bugs caught in production by users

After

  • Maestro flows running iOS + Android
  • CI green on every PR
  • E-commerce checkout covered too
Who you're hiring

Hi, I'm David

David Leuliette with Jacob Krupski and Mazen Chami

With Jacob Krupski (right) behind Maestro and Mazen Chami (left) from Infinite Red.

I've been shipping React Native apps since 2016 — through every breaking-change cycle, every Expo SDK, every New Architecture migration. I'm a top 20 contributor on Stack Overflow for React Native questions, and I curate a directory of React Native tools.

I picked Maestro early because it solves the right problem for mobile end-to-end: write a test in YAML, run it on iOS and Android, sleep at night. I've spent time directly with Jacob Krupski and the Mobile.dev team — so when you hit a weird edge case, you're not the first person hearing about it.

This page is a solo engagement at a flat fee. That means you're hiring me — not an agency, not a junior contractor. The same person who wrote your YAML is the one answering your DM when a flow goes red.

  • Shipping production React Native apps since 2016
  • Solo operator — the person writing your YAML is the person answering your DM

Common questions

One number, agreed upfront, covers everything in scope: setup, the 5 flows, CI wiring, runbook, recorded handoff session, and 14 days of post-handoff support. No hourly billing, no scope-creep invoices. If the work takes longer than 2 weeks because of something on our end, that's our problem, not yours. The exact number depends on your app's complexity — book a 30-minute call and we'll quote on the spot.

Ready to ship with confidence?

Book a 30-minute call. We’ll look at your app, scope the 5 flows, and confirm the timeline. If it’s not the right fit, we’ll say so.

Book a Discovery Call