Maestro is built on learnings from its predecessors (Appium, Espresso, UIAutomator, XCTest) and allows you to easily define and test your Flows.
What are Flows? Think of Flows as parts of the user journey in your app. Login, Checkout and Add to Cart are three examples of possible Flows that can be defined and tested using Maestro.
Built-in tolerance to flakiness. UI elements will not always be where you expect them, screen tap will not always go through, etc. Maestro embraces the instability of mobile applications and devices and tries to counter it.
Built-in tolerance to delays. No need to pepper your tests with sleep()
calls. Maestro knows that it might take time to load the content (i.e. over the network) and automatically waits for it (but no longer than required).
Blazingly fast iteration. Tests are interpreted, no need to compile anything. Maestro is able to continuously monitor your test files and rerun them as they change.
Declarative yet powerful syntax. Define your tests in a yaml
file.
Simple setup. Maestro is a single binary that works anywhere.
# flow_contacts_android.yamlappId: com.android.contacts---- launchApp- tapOn: "Create new contact"- tapOn: "First Name"- inputText: "John"- tapOn: "Last Name"- inputText: "Snow"- tapOn: "Save"
Platform | Support |
---|---|
iOS | ✅ |
Android | ✅ |
Flutter | ✅ |
ReactNative | ✅ |
Blog Post: Introducing: Maestro — Painless Mobile UI Automation
GitHub Repository: https://github.com/mobile-dev-inc/maestro
Public Slack Channel: Join the workspace , then head to the #maestro
channel
Get started by installing the Maestro CLI: