Marathon Cloud vs emulator.wtf
emulator.wtf runs Espresso and instrumentation tests on Android with several sharding modes, up to 10 flaky-test attempts, and JUnit XML, logcat and video outputs. Marathon Cloud runs Android and iOS suites using Espresso, XCUITest and Maestro, with history-driven retries and Allure reporting.
| emulator.wtf | Marathon Cloud | |
|---|---|---|
| Platforms | Android only. | Android and iOS. |
| Frameworks | Espresso and instrumentation tests. | Espresso, XCUITest and Maestro. |
| Retries | --num-flaky-test-attempts, up to 10 attempts. | Failed tests rerun on a different device; tests with a flaky history are retried preventively. |
| Sharding | Targeted-runtime, balanced, even, uniform or explicit sharding. | Device pool sized from your suite's history, targeting 15 minutes per run. |
| Reporting | Merged JUnit XML, logcat and video; web results UI; Gradle plugin. | Allure, JUnit XML, HTML timeline, per-test video and device logs. |
Competitor facts verified 2026-09-29 from the vendor's public pages.
An emulator.wtf alternative for Android and iOS native UI tests
emulator.wtf runs Espresso and instrumentation tests on Android, with configurable sharding and up to 10 flaky-test attempts. Marathon Cloud runs Android and iOS suites with Espresso, XCUITest and Maestro, history-driven retries, and Allure reporting.
Choose emulator.wtf when
- You run Android Espresso or instrumentation tests only.
- You want targeted-runtime, balanced, even, uniform or explicit sharding.
Choose Marathon Cloud when
- You also run XCUITest or Maestro on iOS.
- You want flaky-test retries driven by per-test history on a different device.
- You want Allure reports alongside JUnit XML, per-test video and device logs.
What a run costs on Marathon Cloud
A suite with 120 minutes of total test time runs on 8 devices for about 15 minutes: 2 device-hours, $4.00 on Android or $6.00 on iOS.