maestro-debug-test

This Skill automates debugging and fixing failing Maestro E2E tests by analyzing failure artifacts like screenshots and command logs, diagnosing visual or hierarchical discrepancies, and iteratively applying fixes to test scripts until they pass.

Automated test failure diagnosis works by analyzing screenshots, command logs, and device hierarchy to pinpoint the root cause of Maestro E2E test failures, applying targeted fixes like adjusting selectors or adding waits, and re-running tests efficiently.

Yes, you need the Maestro CLI and device interaction tools installed in your environment, as this Skill requires Maestro CLI execution and device interaction tools to run tests, analyze device states, and apply fixes through Maestro MCP commands.

The best way to handle Maestro test failures in a CI/CD pipeline is using an automated debugging loop that executes tests with specified flags, analyzes failure artifacts, and iteratively applies targeted fixes to selectors and waits without manual intervention.

Maestro E2E tests fail due to visual or hierarchical discrepancies when the device state does not match the test script expectations, requiring analysis of screenshots and device hierarchy to diagnose and apply fixes like adjusting selectors or adding waits.

Yes, you can use this Skill with existing Maestro test scripts by pointing it to your test file path, such as 'tests/login.yml', and it will execute the test, diagnose any failures, and apply iterative fixes to the script.