Mobile UI Testing with Maestro

VerifiedCaution

Write and run mobile UI tests using Maestro's YAML-based flow definitions. Helps with element inspection, platform-specific behaviors, and CI integration. Ideal for teams wanting simple, readable tests understandable by non-developers.

Sby Skills Guide Bot
TestingIntermediate
6/2/2026
Claude Code
#mobile-testing#ui-testing#yaml#ios#android

Recommended for

Automated summary

Maestro is a mobile UI testing framework using simple YAML flows, enabling testing of iOS and Android apps.

Strengths

  • YAML syntax readable by non-developers
  • Maestro Studio for real-time element inspection
  • Support for environment variables and conditional flows

Limitations

  • Does not support gray-box testing like Detox
  • Flows can become cumbersome with many conditions
When to use it

Use Maestro for simple, maintainable mobile UI tests, especially in mixed teams of developers and QA.

When not to use it

Avoid Maestro if you need deep native-level testing or integration with mobile unit test frameworks.

Security analysis

Caution
Quality score92/100

The skill provides a Maestro setup command that downloads and executes a script from the internet with no integrity checks. While the official Maestro URL is expected, this is a common risky pattern that should include a warning or alternative verification method.

Findings
  • •Instructs piping a remote script directly into bash (curl | bash) without verification, which could lead to arbitrary code execution if the source is compromised.
How this analysis is made

Examples

Login flow
Write a Maestro flow that tests a login screen with email and password, then asserts a welcome message.
Environment variables
Help me create a Maestro flow that uses environment variables for credentials and runs with a shell command.
Conditional onboarding
Create a Maestro flow that handles optional notification permission popups during onboarding.

name: maestro description: When the user wants to write mobile UI tests using Maestro's simple YAML-based flow definitions. Also use when the user mentions "maestro," "mobile UI testing," "YAML mobile tests," "maestro flows," or "maestro studio." For React Native-specific gray-box testing, see detox. For cross-platform mobile automation, see appium. metadata: author: terminal-skills version: "1.0.0" category: development tags: - mobile-testing - ui-testing - yaml - ios - android

Maestro

Overview

You are an expert in Maestro, the mobile UI testing framework that uses simple YAML flows. You help users write readable test flows, use Maestro Studio for element inspection, handle platform-specific behaviors, set up test suites, and integrate Maestro into CI. You value Maestro's simplicity — most tests should be understandable by non-developers.

Instructions

Initial Assessment

  1. Platform — iOS, Android, or both?
  2. App — How is the app built and installed?
  3. Flows — What user journeys need testing?
  4. CI — Cloud (Maestro Cloud) or self-hosted?

Setup

# setup-maestro.sh — Install Maestro and verify it works.
# Works on macOS and Linux.

# Install
curl -Ls "https://get.maestro.mobile.dev" | bash

# Verify
maestro --version

# Launch Maestro Studio (interactive element inspector)
maestro studio

Basic Flow

# flows/login.yaml — Maestro flow testing the login screen.
# Taps, types, and asserts in plain YAML.
appId: com.example.myapp
---
- launchApp
- tapOn: "Email"
- inputText: "user@example.com"
- tapOn: "Password"
- inputText: "password123"
- tapOn: "Log In"
- assertVisible: "Welcome back"

Complete User Journey

# flows/purchase-flow.yaml — End-to-end purchase flow from browse to checkout.
# Demonstrates navigation, scrolling, and multi-step interaction.
appId: com.example.shop
---
- launchApp
- assertVisible: "Featured Products"

# Browse products
- tapOn: "Categories"
- tapOn: "Electronics"
- scrollUntilVisible:
    element: "Wireless Headphones"
    direction: DOWN
- tapOn: "Wireless Headphones"

# Add to cart
- assertVisible: "Wireless Headphones"
- assertVisible: "$79.99"
- tapOn: "Add to Cart"
- assertVisible: "Added to cart"

# Checkout
- tapOn: "Cart"
- assertVisible: "1 item"
- tapOn: "Checkout"
- inputText: "4242424242424242"
- tapOn: "Pay Now"
- assertVisible: "Order confirmed"

Conditional and Repeated Flows

# flows/onboarding.yaml — Handle conditional onboarding screens.
# Uses runFlow for reusable sub-flows and conditional logic.
appId: com.example.myapp
---
- launchApp

# Dismiss notification permission if it appears
- runFlow:
    when:
      visible: "Allow Notifications"
    commands:
      - tapOn: "Not Now"

# Skip onboarding carousel
- tapOn: "Skip"
- assertVisible: "Sign Up"

Environment Variables

# flows/login-env.yaml — Login flow using environment variables.
# Keeps credentials out of the flow file.
appId: com.example.myapp
---
- launchApp
- tapOn: "Email"
- inputText: "${EMAIL}"
- tapOn: "Password"
- inputText: "${PASSWORD}"
- tapOn: "Log In"
- assertVisible: "Welcome back"
# run-with-env.sh — Run Maestro flow with environment variables.
# Pass sensitive data at runtime.
EMAIL=user@example.com PASSWORD=secret123 maestro test flows/login-env.yaml

Screenshots and Recording

# flows/visual-check.yaml — Take screenshots at key points for visual verification.
# Useful for design review and regression checks.
appId: com.example.myapp
---
- launchApp
- assertVisible: "Home"
- takeScreenshot: "home-screen"
- tapOn: "Profile"
- assertVisible: "Profile"
- takeScreenshot: "profile-screen"

Running Tests

# run-maestro.sh — Common Maestro commands.
# Run single flows, suites, and with recording.

# Run single flow
maestro test flows/login.yaml

# Run all flows in a directory
maestro test flows/

# Record a video of the test
maestro record flows/login.yaml

# Use Maestro Studio to inspect elements
maestro studio

CI Integration

# .github/workflows/maestro.yml — Run Maestro tests in CI.
# Uses Android emulator on Ubuntu runner.
name: Maestro E2E
on: [push]
jobs:
  maestro:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-java@v4
        with:
          distribution: temurin
          java-version: 17
      - name: Install Maestro
        run: curl -Ls "https://get.maestro.mobile.dev" | bash
      - name: Start emulator and run tests
        uses: reactivecircus/android-emulator-runner@v2
        with:
          api-level: 34
          script: |
            adb install app-debug.apk
            ~/.maestro/bin/maestro test flows/

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/mobile-ui-testing-with-maestro-mmh8qryp/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/mobile-ui-testing-with-maestro-mmh8qryp' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mobile-ui-testing-with-maestro-mmh8qryp/download' --output '.skill-downloads/mobile-ui-testing-with-maestro-mmh8qryp/SKILL.md.part' && mv '.skill-downloads/mobile-ui-testing-with-maestro-mmh8qryp/SKILL.md.part' '.skill-downloads/mobile-ui-testing-with-maestro-mmh8qryp/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Setup
# setup-maestro.sh — Install Maestro and verify it works.
# Works on macOS and Linux.

# Install
curl -Ls "https://get.maestro.mobile.dev" | bash

# Verify
maestro --version

# Launch Maestro Studio (interactive element inspector)
maestro studio

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/mobile-ui-testing-with-maestro-mmh8qryp/SKILL.md' && test -s '.skill-downloads/mobile-ui-testing-with-maestro-mmh8qryp/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/maestro' && cp -R '.skill-downloads/mobile-ui-testing-with-maestro-mmh8qryp' '.claude/skills/maestro'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/mobile-ui-testing-with-maestro-mmh8qryp'

openskills read 'mobile-ui-testing-with-maestro-mmh8qryp'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/mobile-ui-testing-with-maestro-mmh8qryp/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills