maestro-fix-cycle

What problem does it solve?

Reduces manual debugging and cascading failures in Maestro mobile test suites by running an automated, stateful repair loop that processes failing flows one at a time, analyzes root causes, applies targeted fixes to YAML flows or app code, and verifies outcomes until the suite stabilizes.

Core Features & Use Cases

• Stateful, resumable cycle: Persists progress, history, and learned patterns in a .maestro-cycle directory so the loop can resume after interruptions.
• Failure analysis and targeted fixes: Parses Maestro output to identify failing steps, matches known patterns (text-mismatch, missing-testid, locale issues), and either updates flow YAML, shared sub-flows, or suggests/apply app code fixes.
• Verification and safety limits: Re-runs flows to verify fixes, enforces max iterations per flow, prioritizes shared sub-flows to avoid cascading failures, and records all changes in an append-only history for audit.
• Use Cases: Nightly CI repair runs for flaky UI tests, developer workflows to auto-fix regressions after UI refactors, and maintenance runs to keep large Maestro suites healthy.

Quick Start

Start maestro-fix-cycle to analyze the current failing Maestro mobile flows, apply iterative fixes one flow at a time, and continue until the suite passes.