skills.rest
parisgroup-ai
parisgroup-aiOFFICIAL
Explore all skills by this author →
GitHub

maestro-analyze

Analyze Maestro run failures and reconstructs a prioritized diagnosis in maestro-diagnosis.yaml.

1|2|Updated Apr 6, 2026
Search Tags:#diagnostics#i18n#test-automation#failure-analysis#maestro#mobile-testing#selector-validation
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill maestro-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maestro-analyze
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/maestro-analyze
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill maestro-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about maestro-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose Maestro mobile test failures from run artifacts?▼

Diagnose Maestro mobile test failures by parsing maestro-run-result.yaml to reconstruct failing flow steps, correlating selectors to app source files, and producing a confidence-ranked maestro-diagnosis.yaml with suggested fixes.

What causes Maestro flow selector mismatches in mobile apps?▼

Maestro flow selector mismatches occur when i18n resource labels change or testID props are missing. Analyzing app source files correlates failing selectors to actual component text to identify text-mismatch or missing-testid root causes.

How do I troubleshoot intermittent animation timing flakiness in Maestro tests?▼

Troubleshoot intermittent animation timing flakiness by analyzing Maestro run artifacts to rebuild a failure timeline, detecting known animation-timing failure patterns, and generating prioritized fixes in a maestro-diagnosis.yaml file.

Can I detect locale-dependent selector problems in Maestro mobile testing?▼

Detect locale-dependent selector problems by checking i18n resources and testIDs during Maestro mobile testing analysis. The process identifies locale-mismatch patterns and maps selectors to changed labels across different language resources.

How do I fix mockNetwork failures in Maestro test automation flows?▼

Fix mockNetwork failures in Maestro test automation by analyzing run artifacts to detect network-mock-miss patterns. The analysis produces batchable fixes with file and line correlations for maintainers in a maestro-diagnosis.yaml deliverable.

Does Maestro failure analysis require app source files to diagnose test errors?▼

Maestro failure analysis requires parsing maestro-run-result.yaml and app source files to correlate selectors to source lines. Checking i18n resources and testIDs is necessary to produce accurate confidence-ranked diagnoses.

Related Skills

Explore More Software Engineering Skills→
CodySwannGTCodySwannGT
3

playwright-selectors

Define Playwright selector best practices for Expo web apps using testID and aria-label.

Community
Basic
parisgroup-aiparisgroup-ai
1

maestro-fix-cycle

Analyze failing Maestro YAML flows and apply iterative repairs.

Official
Advanced
parisgroup-aiparisgroup-ai
1

maestro-run

Run Maestro end-to-end test flows on iOS Simulator with automatic project discovery.

Official
Advanced
synaptiaisynaptiai
4

detect

Detect patterns in logs, text, or code with evidence anchors and confidence scores.

Official
Intermediate