maestro-run-test

Execute Maestro E2E tests from files or directories with tag filtering.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/luigiinred/dotfiles --skill maestro-run-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro-run-test
Source: https://github.com/luigiinred/dotfiles/tree/main/dot_cursor/skills/maestro-run-test
Command: npx skills add https://github.com/luigiinred/dotfiles --skill maestro-run-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the execution of Maestro End-to-End (E2E) tests, providing clear reporting on test outcomes and facilitating debugging.

Core Features & Use Cases

  • Execute Maestro Tests: Run single test files or entire directories of Maestro flows.
  • Output Capture: Saves test results, including logs and screenshots, to a dedicated directory.
  • Conditional Execution: Supports filtering tests using tags (--include-tags, --exclude-tags).
  • Use Case: When you need to verify the functionality of your application's user interface through automated E2E testing, especially after code changes.

Quick Start

Run the Maestro test located at maestro/flows/auth/LoginWithGustoWelcome.yml and save the results.

Frequently Asked Questions about maestro-run-test

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

FAQPage Schema
How do I run Maestro E2E tests from a specific directory?

To run Maestro E2E tests, execute the test command targeting your specified directory or file path. The execution captures detailed output, including logs and screenshots, saving them directly to a designated results directory for review.

Can I filter Maestro test execution by tags?

Yes, you can filter Maestro test execution using tags. The system supports conditional execution through `--include-tags` and `--exclude-tags` parameters, allowing you to selectively run or skip specific test flows within your directory.

Does Maestro test execution capture screenshots on failure?

Maestro test execution captures comprehensive reporting of test pass/fail statuses, error messages, and screenshots. All output and artifacts are automatically saved to a dedicated results directory to facilitate debugging.

What is the best way to debug a failing Maestro E2E flow?

The best way to debug a failing Maestro E2E flow is to review the dedicated results directory. The execution output provides comprehensive reporting, capturing detailed error messages and screenshots to pinpoint UI failures.

How do I execute Maestro tests on a specific device?

You can execute Maestro tests on a specific device by utilizing the advanced device selection options during test execution. This ensures your E2E flows run against the targeted environment while capturing output.