Skip to content

monster-4y/maestro

This branch is 649 commits behind mobile-dev-inc/Maestro:main.

Folders and files

NameName
Last commit message
Last commit date
Jan 31, 2023
Jan 31, 2023
Aug 18, 2022
Aug 18, 2022
Apr 1, 2022
Jan 31, 2023
Feb 9, 2023
Feb 10, 2023
Feb 9, 2023
Feb 10, 2023
Dec 15, 2022
Feb 6, 2023
Feb 6, 2023
Jan 20, 2023
Feb 8, 2023
Feb 9, 2023
Feb 8, 2023
Jan 2, 2023
Feb 9, 2023
Aug 30, 2022
Jan 20, 2023
Dec 14, 2022
Apr 1, 2022
Sep 19, 2022
Feb 9, 2023
Apr 1, 2022
Nov 6, 2022
Jan 25, 2023
Jul 11, 2022
Nov 23, 2022
Apr 1, 2022
Feb 10, 2023
Apr 1, 2022
Apr 1, 2022
Dec 13, 2022
Jan 31, 2023

Repository files navigation

Maestro 🎹

Maestro is the easiest way to automate UI testing for your mobile app.

Note Full documentation for Maestro can be found at maestro.mobile.dev

Why Maestro?

Maestro is built on learnings from its predecessors (Appium, Espresso, UIAutomator, XCTest)

  • 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.

Resources

About

Painless Mobile UI Automation

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Kotlin 81.5%
  • TypeScript 13.0%
  • Swift 3.2%
  • JavaScript 1.5%
  • Shell 0.8%
  • HTML 0.0%