Suggest a tool

Maestro vs EarlGrey: open-source mobile automation tools compared

Metrics as of , from the GitHub or GitLab API of each repository. Refreshed monthly.

Summary

Maestro: Framework for UI and end-to-end testing of Android, iOS and web apps using YAML flows.

EarlGrey: UI automation test framework for native iOS apps with automatic synchronization; version 1.0 is deprecated for EarlGrey 2.

Both are listed under Mobile automation. The table gives repository metrics from the GitHub API with their fetch date, then the documented facts used for every comparison in this category, each linked to the README or docs page it comes from. A cell reads "not documented" when the fact was not found in the project's documentation (3 of 14 fact cells here); that does not mean the feature is absent.

Side by side

Maestro and EarlGrey: metrics and documented facts, in the fixed row order used for mobile automation comparisons.
FactMaestroEarlGrey
Stars15,75215,7001
Forks96617371
Contributors1211571
Last release2026-08-3112022-06-071
Last commit2026-09-1812023-09-091
Commits in 90 days97101
LicenseApache-2.01Apache-2.01
Primary languageKotlin1Objective-C1
Statusactive1inactive1
Languages for writing testsYAML flow files source: READMESwift (3.0 and 2.3) and Objective-C test targets source: Docs: Install and Run
Mobile platformsAndroid, iOS and web on emulators, simulators, browsers and physical Android devices source: READMENative iOS apps source: README
Test authoring formatYAML commands such as launchApp, tapOn, assertVisible; visual flow building in Maestro Studio source: READMECode with XCTest; runs from Xcode or xcodebuild source: README
Parallel or distributed executionCLI sharding across connected devices (--shards, --shard-split, --shard-all) source: Docs: Maestro CLI commands and optionsnot documentednot found in the project's documentation as of
CI integrationReport formats for Jenkins, GitHub Actions and Azure DevOps source: Docs: Test reports and artifactsnot documentednot found in the project's documentation as of
Report formatsJUnit XML, HTML, HTML detailed (--format flag) source: Docs: Test reports and artifactsnot documentednot found in the project's documentation as of
Install methodInstall script (curl -fsSL "https://get.maestro.mobile.dev" | bash); requires Java 17 or higher source: READMECocoaPods, Carthage or manual Xcode project setup source: Docs: Install and Run

1 Fetched from the GitHub or GitLab API on . Hover a value for its own date.

When each fits

Written from each project's documented scope, not from preference. Neither tool is ranked.

Maestro

Fits projects that run UI and end-to-end tests for Android, iOS and web apps; its README describes tests kept as a flat list of YAML commands. source: README

EarlGrey

Fits projects that write UI tests for native iOS apps with XCTest; its README describes automatic synchronization with the UI, network requests and various queues. source: README

More on these tools

Sources

  1. GitHub REST API: repository, read
  2. GitHub REST API: repository, read
  3. GitHub REST API: contributors, read
  4. GitHub REST API: contributors, read
  5. GitHub REST API: latest release, read
  6. GitHub REST API: latest release, read
  7. GitHub REST API: commits, read
  8. GitHub REST API: commits, read
  9. README, read
  10. Docs: Install and Run, read
  11. README, read
  12. Docs: Maestro CLI commands and options, read
  13. Docs: Test reports and artifacts, read

Documented facts collected 2026-09-22. See the methodology for how metrics and facts are gathered.