Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From Harness Mobile
Maestro cross-platform mobile E2E conventions — one declarative YAML flow per user journey under .maestro/, stable testID/accessibility-label selectors over coordinates, local/Studio/Cloud run modes, and the Feb 2026 Maestro MCP. Use when authoring or running Maestro end-to-end flows for any iOS, Android, React Native, or Flutter target.
npx claudepluginhub camilool8/harness-engineering-templates --plugin harness-mobileHow this skill is triggered — by the user, by Claude, or both
Slash command
/harness-mobile:addon-maestro-e2eThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
`maestro` is the 2026 cross-platform E2E tool — adopted by Microsoft, Meta, DoorDash. Declarative YAML flows, robust to UI changes.
Runs automated patient safety test suites for healthcare deployments, blocking on CRITICAL failures in CDSS accuracy, PHI exposure, and data integrity.
Share bugs, ideas, or general feedback.
maestro is the 2026 cross-platform E2E tool — adopted by Microsoft, Meta, DoorDash. Declarative YAML flows, robust to UI changes.
.maestro/<journey>.yaml.testID (RN) / accessibility identifiers (native) / Semantics labels (Flutter) as selectors.tapOn with text labels for hardiness; avoid coordinates.maestro test .maestro/login.yaml.maestro studio for interactive flow authoring.maestro cloud --apiKey $MAESTRO_API_KEY for parallel cross-device runs.A Maestro MCP shipped Feb 2026. When wired, the agent can boot device, run flows, and read structured pass/fail output without shelling out. Treat it as preferred when available.