On this page
The main mobile E2E testing frameworks are Appium, Maestro, Detox, Espresso, XCUITest, Flutter integration_test, Patrol, WebdriverIO and Revyl. Choose by stack and test format; Revyl runs natural-language tests on cloud iOS simulators and Android emulators. As of November 2026, Revyl's Free plan includes up to 1,200 free device minutes a month on iOS, Android, web and Mac, with no card and no monthly fee.
- Free tier
- Appium: Yes
- Maestro: Yes
- Detox: Yes
- Espresso: Yes
- XCUITest: Yes
- Patrol: Yes
- WebdriverIO: Yes
- Revyl: Yes
- CLI
- Appium: Yes
- Maestro: Yes
- Detox: Yes
- Espresso: Not verified
- XCUITest: Not verified
- Patrol: Yes
- WebdriverIO: Yes
- Revyl: Yes
- Parallel sessions
- Appium: Not verified
- Maestro: Yes
- Detox: Yes
- Espresso: Not verified
- XCUITest: Yes
- Patrol: Yes
- WebdriverIO: Yes
- Revyl: Yes
- MCP server
- Appium: Yes
- Maestro: Yes
- Detox: Not verified
- Espresso: Not verified
- XCUITest: Not verified
- Patrol: Yes
- WebdriverIO: Yes
- Revyl: Yes
YesNot verified
Show as a table with sourcesHide table
Scroll the table sideways to see all 3 columns.
How do you choose a mobile app testing tool?
The main mobile app testing tools for end-to-end tests are Appium, Maestro, Detox, Espresso, XCUITest, Flutter integration_test, Patrol, WebdriverIO and Revyl, and the right one depends on your app stack and who writes the tests. Native Android code points to Espresso, native iOS code to XCUITest, React Native to Detox, and Flutter to integration_test or Patrol. Teams that want one suite for both platforms, written outside the app, look at Appium, Maestro or WebdriverIO. Then decide where the tests run: on your own machines and CI, or on a hosted service.
The frameworks also differ in how they reach the app. Espresso tests are instrumented tests that run with access to the app. Apple says XCUITest automation runs independently from the app. Detox installs native code alongside the app and calls itself gray-box. Maestro drives the app from the UI layer, and Appium sends commands through platform drivers.
What are the main mobile E2E testing frameworks?
Appium
Appium is an open-source automation server built on the W3C WebDriver protocol. Tests are code in a WebDriver client, such as JavaScript, Java or Python, and official drivers reach iOS, Android, browsers and more. Appium fits teams that want tests as code in an existing language and targets beyond phones. Appium requires Node.js, the server, a driver per platform and that platform’s SDK. Appium MCP adds natural-language element finding and Java/TestNG test generation. Appium is free under Apache 2.0.
Maestro
Maestro runs tests as YAML flows from a small CLI, against Android emulators and devices, iOS simulators and web apps. Maestro fits teams that want readable tests that people outside the test team can edit. Teams that need tests as general-purpose code will find Appium or the native frameworks closer to that model. The Maestro MCP server ships in the CLI. The CLI is free under Apache 2.0, and Maestro Cloud is $250 per device per month as of November 2026.
Detox
Detox is Wix’s gray-box E2E framework for mobile apps, built from the ground up for React Native. Tests are JavaScript, usually run with Jest, and Detox monitors asynchronous work in the app to keep tests in sync. Detox fits React Native teams that want tests in the same language as the app. Native-only apps have Espresso and XCUITest as first-party options. Detox is free under MIT.
Espresso
Espresso is Google’s Android UI testing API, part of AndroidX Test. Tests are Kotlin or Java, live in the app module, and wait for the app to be idle before each action. Espresso fits Android developers who own the code. Cross-platform teams need a second framework for iOS. Espresso is free under Apache 2.0.
XCUITest
XCUITest is Apple’s UI testing framework, written with XCTest in Swift or Objective-C. Xcode records interactions as code, and test plans replay tests across locales, device types and system conditions. XCUITest fits teams building for Apple platforms in Xcode. Android needs a separate framework. XCUITest is free with Xcode and needs a Mac.
Flutter integration_test
Flutter’s integration_test package is the official way to test a whole Flutter app. Tests are Dart and use flutter_test APIs, and they run on devices, emulators, web and desktop, or on Firebase Test Lab. It fits Flutter teams that want the SDK’s own path. The package is free under the BSD-3-Clause license.
Patrol
Patrol is LeanCode’s open-source framework for Flutter apps. Patrol tests are Dart, and Patrol adds native interactions that integration_test leaves out, such as permission dialogs, notifications and WebViews. Patrol 4.0 added web support, and Patrol MCP lets AI assistants run and monitor Patrol sessions. Patrol is free under Apache 2.0, and LeanCode sells setup and test-writing services.
WebdriverIO
WebdriverIO is an open-source test runner for web, mobile and desktop apps under the OpenJS Foundation. For mobile, WebdriverIO automates Android and iOS through Appium, so one API covers browser and app tests. WebdriverIO documents agent features, including an MCP server. WebdriverIO fits JavaScript teams that already test the web with it. WebdriverIO is free under MIT.
Revyl
Revyl, the hosted entry on this list, builds the app, runs it on cloud iOS simulators and Android emulators, and runs tests written as natural-language steps or YAML. Each Revyl test run produces a report with video, step timeline and device logs, and Atlas fills in with the screens that observed sessions, tests and explorations capture. With proof of changes, Revyl posts a verdict on the pull request. Revyl fits teams, and coding agents, that want E2E checks that leave evidence for each test run. People, CI jobs and coding agents drive Revyl through its CLI and MCP server.
As of November 2026, Revyl’s Free plan is $0 and includes up to 1,200 free device minutes a month on iOS, Android, web and Mac and 2 devices at once with no card. Revyl’s Pro plan is pay as you go at $0.075 per device minute on iOS and Android and $0.05 a minute on web and Mac, with 10 devices at once, free minutes every month, a $20 starting credit and no monthly fee. Every plan covers unlimited developers and agents with no seat fees. Enterprise pricing is custom, with volume pricing and unlimited devices at once. Maestro Cloud is $250 per device per month.
Where can you run these tests in the cloud?
Hosted options depend on the framework. Xcode Cloud runs XCTest UI tests and includes 25 compute hours a month with Apple Developer Program membership. Maestro Cloud runs Maestro flows. Device clouds such as AWS Device Farm and BrowserStack App Automate run Appium, Espresso and XCUITest suites. Firebase Test Lab also runs Android instrumentation and XCTest tests, but Google has deprecated it and will shut it down on September 30, 2027.
Revyl runs Revyl tests on its own cloud sessions. A Revyl Mac computer comes with Xcode and the iOS Simulator, runs XCUITest suites with xcodebuild test, and runs Maestro iOS flows in a GitHub Actions job with runs-on: revyl-macos, as the Maestro iOS cookbook shows. For existing suites, Revyl documents a source-installed Appium driver and Maestro runner, which run the native commands listed in their docs. Revyl’s revyl-cli-import-tests agent skill converts suites from frameworks such as Appium, Maestro, XCUITest, Espresso and Detox into Revyl tests for a person to review.
Beyond mobile app testing: what else Revyl runs
An E2E framework decides how a test is written. The Revyl account that runs those tests also runs:
- Web: Revyl runs Chrome browser sessions from a bundle it builds or from a deployed preview URL, and tests run against web builds the same way as against iOS and Android builds. Web testing is on every plan.
- iOS simulators: revyl build produces a simulator .app on cloud runners, and the app runs on a cloud iOS simulator.
- Android emulators: Revyl’s natural-language tests also run on cloud Android emulators from an Android build.
- macOS computers: a Revyl Mac computer is a full macOS environment in the cloud with Xcode and the iOS Simulator, which an agent or a person starts, uses and stops while the desktop streams to the browser.
revyl computer execruns commands such asxcodebuild test, and a GitHub Actions job withruns-on: revyl-macosgets a single-use Revyl Mac. - Atlas: Atlas records the screens, states and transitions that Revyl runs observe, each tied to its screenshots.
- Agent access: people, CI jobs and coding agents drive all of this through the Revyl CLI and the MCP server.
- Reports and PR verdicts: each test run produces a report with video, a step timeline and device logs, and with proof of changes, Revyl posts a verdict on the pull request.
Sources
Facts were checked against these public pages on November 11, 2026. Spot an error? Email support@revyl.ai and we will correct it.
- Appium in a nutshell
- Appium requirements
- Appium MCP
- Maestro supported platforms
- Maestro MCP server
- Maestro pricing
- Detox
- How Detox works
- Espresso overview
- Android instrumented tests
- XCTest documentation
- WWDC25: Record, replay, and review: UI automation with Xcode
- Flutter integration tests
- Patrol
- Patrol MCP
- WebdriverIO mobile
- WebdriverIO and AI agents
- Xcode Cloud
- AWS Device Farm FAQ
- BrowserStack App Automate
- Firebase Test Lab
- Revyl test reports
- Revyl Atlas
- Revyl proof of changes
- Revyl Appium driver
- Revyl Maestro runner
- Revyl agent skills
- Revyl pricing
- appium.io/docs/en/latest/ecosystem/drivers
- github.com/appium/appium/blob/master/LICENSE
- docs.maestro.dev/get-started/what-is-maestro.md
- github.com/wix/Detox
- github.com/android/android-test
- developer.apple.com/library/archive/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/09-ui_testing.html
- developer.apple.com/documentation/safari-developer-tools/installing-xcode-and-simulators
- docs.flutter.dev/cookbook/testing/integration/introduction
- raw.githubusercontent.com/flutter/flutter/master/LICENSE
- leancode.co/blog/patrol-4-0-release
- patrol.leancode.co/pricing
- webdriver.io
- github.com/webdriverio/webdriverio
- docs.revyl.com/reference/step-types
- docs.revyl.com/concepts
Frequently asked questions
What else does Revyl do?
One Revyl account runs Chrome sessions for web builds, cloud iOS simulators and Android emulators for E2E suites, and Revyl Mac computers with Xcode and the iOS Simulator. Atlas builds up from the screens its runs observe, the CLI and MCP server let people and coding agents drive all of it, and each test run produces a report, with a PR verdict from proof of changes.
Which mobile testing frameworks are free?
All eight frameworks on this page are free to use: Appium, Maestro, Detox, Espresso, XCUITest, Flutter integration_test, Patrol and WebdriverIO. You still pay for the devices, Macs and CI minutes that run them, and hosted options such as Maestro Cloud or Xcode Cloud have their own prices.
Which frameworks test iOS and Android with one suite?
Appium, Maestro, Detox and WebdriverIO run one suite against both platforms, and so do Flutter integration_test and Patrol for Flutter apps. Espresso targets Android and XCUITest targets Apple platforms.
Which mobile testing frameworks work with AI coding agents?
Appium, Maestro, Patrol and WebdriverIO each document an MCP server that coding agents can use. Revyl also has an MCP server and a CLI that agents use to start cloud devices and run tests.
Can I write mobile E2E tests in plain English?
Some tools support it. Revyl tests are natural-language steps such as 'Tap the login button'. Maestro's MCP server turns a plain-language request into a YAML flow, and WebdriverIO v10 adds browser.act() for steps written as intent. Espresso, XCUITest, Detox and Flutter integration_test tests are code.
Where can I run mobile E2E tests in the cloud?
Xcode Cloud runs XCTest UI tests, Maestro Cloud runs Maestro flows, and device clouds such as AWS Device Farm and BrowserStack run Appium, Espresso and XCUITest suites. Firebase Test Lab also runs Espresso and XCTest tests, but Google will shut it down on September 30, 2027.