maestro

Run Maestro native E2E flows against an installed simulator/emulator build.

archibald maestro|mae [options]

The command preflights the host's Maestro CLI installation. If maestro is not found on PATH (or in ~/.maestro/bin), it prints platform-specific install instructions and exits non-zero before any flow runs.

Options

Option	Description
`-f, --flows [path]`	Path (file or directory) containing Maestro flow YAML. Default: `maestro`.
`-a, --appId [appId]`	Override the `appId` / bundle identifier for this run (forwarded to maestro as `--app-id`).
`-e, --env [KEY=val]`	Inject `KEY=value` into flows (forwarded as `-e KEY=value`). Pass the flag multiple times for multiple entries.
`-h, --help`	Show help commands.

Examples

# Run every flow under maestro/flows
archibald maestro

# Run a single flow
archibald maestro -f maestro/flows/smoke.yaml

# Override the bundle id for a preview build
archibald maestro -a com.example.app.preview

# Inject credentials into the flows
archibald maestro -e MAESTRO_USERNAME=alice -e MAESTRO_PASSWORD=secret

See End-to-end testing → Maestro for guidance on writing flows and the underlying integration.

Options​

Examples​

Options

Examples