maestro-analyze

What problem does it solve?

Rapidly identify why Maestro mobile test flows fail by reconstructing the failing steps, correlating selectors to application code, and surfacing the most likely root causes so engineers and QA can fix flows with confidence.

Core Features & Use Cases

• Failure reconstruction: Read maestro-run-result.yaml and rebuild a failure timeline showing which steps passed, timed out, or errored.
• Code correlation: Search app source and i18n files to map failing selectors to actual component text, testID props, or changed labels.
• Pattern matching & recommendations: Detect known failure classes (text-mismatch, missing-testid, animation-timing, network-mock-miss, locale-mismatch) and produce prioritized suggested fixes.
• Deliverable: Emit a maestro-diagnosis.yaml summarizing diagnoses, confidence scores, batchable fixes, and file/line correlations for maintainers.
• Use cases: Investigating login button mismatches, intermittent animation-related flakiness, mockNetwork failures, and locale-dependent selector problems.

Quick Start

Run maestro-analyze to inspect apps/mobile/maestro-run-result.yaml, reconstruct failing steps, correlate selectors to source files, and produce a maestro-diagnosis.yaml with suggested fixes.