← ClaudeAtlas

maestro-analyzelisted

Investigate why a Maestro mobile test on the iOS Simulator failed. Use after a mobile/simulator test fails and you need the cause. Triggers on: teste mobile falhou, porque o teste do app quebrou, analisar falha mobile, maestro falhou, mobile test failed, ios simulator error.
parisgroup-ai/imersao-ia-setup · ★ 1 · AI & Automation · score 74
Install: claude install-skill parisgroup-ai/imersao-ia-setup
# maestro-analyze - Maestro Failure Analysis Analyze Maestro flow failures with step reconstruction, code correlation, selector validation, and pattern matching. ## Usage ```bash /maestro-analyze # Analyze last run (from maestro-run-result.yaml) /maestro-analyze <flow> # Analyze specific flow ``` ## Analysis Steps ### Step 1: Load Last Run ```bash cat apps/mobile/maestro-run-result.yaml ``` If no result file exists, prompt user to run `/maestro-run` first. ### Step 2: For Each Failure, Reconstruct Flow Steps Read the failing YAML flow and the Maestro output to reconstruct what happened: ```yaml failure_timeline: flow: "auth/login.yaml" steps: - step: "launchApp (clearState: true)" status: "ok" - step: "waitForAnimationToEnd" status: "ok" - step: "tapOn: 'Email'" status: "ok" - step: "inputText: ${TEST_EMAIL}" status: "ok" - step: "tapOn: 'Sign In'" status: "timeout" error: "Element 'Sign In' not found after 5000ms" app_state: screen: "login" visible_elements: ["Email field", "Password field", "Log In button"] ``` ### Step 3: Code Correlation For each failure, correlate with app source code: ```yaml code_correlation: failing_selector: "Sign In" selector_type: "text" search_results: - query: "grep -r 'Sign In' apps/mobile/app/" found: false - query: "grep -r 'Log In' apps/mobile/app/" found: true file: "apps/mobile/app/(auth)/login.tsx"