Tinder: 3-hour test cycles to 20 minutes

Anton Malinskiy ·

The problem

Tinder runs 1,400 Android Espresso tests and 1,300 iOS UI tests daily. Their infrastructure couldn’t keep up:

Android: 30 AWS Genymotion emulators. Unstable. Poor sharding. Long queue times.

iOS: 16 AWS Mac EC2 instances. 80% test stability. Manual maintenance after every Apple release. 3-hour test cycles.

DevOps spent more time maintaining test infrastructure than supporting product work.

What changed

Tinder replaced everything with Marathon Cloud. Setup took 2-3 minutes per engineer — upload APK/IPA, run tests. No infrastructure provisioning.

Android results:

  • Full 1,400-test suite per PR in under 20 minutes
  • Zero DevOps intervention required
  • Replaced 30 Genymotion emulators with on-demand virtual devices

iOS results:

  • 3 hours → 20 minutes
  • Stability: 80% → 98%
  • No more manual Mac instance updates after Xcode releases

By the numbers

Test cycle time ........ 3 hours    → < 20 min
iOS stability .......... ~80%       →   98%
DevOps time on infra ... 10+ hrs/wk →   ~0
Infrastructure cost .... baseline   →  -60%
Release cadence ........ irregular  →   bi-weekly

Why not BrowserStack or AWS Device Farm?

Marathon Cloud runs virtual devices with automatic sharding and smart retries. No per-device monthly fees — you pay per minute of actual test execution. BrowserStack charges per parallel device slot ($199+/mo each). AWS Device Farm caps at 5 parallel devices by default and costs $0.17/min.

For a team running 1,400+ tests on every PR, the math isn’t close.