run-maestro-release-tests

Runs FeedFlow Maestro E2E suites on Android and iOS and generates HTML and Markdown pass/fail reports.

1.2k|63|Updated Feb 11, 2023
One-click install
npx skills add https://github.com/prof18/feed-flow --skill run-maestro-release-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-maestro-release-tests
Source: https://github.com/prof18/feed-flow/tree/main/.ai/skills/run-maestro-release-tests
Command: npx skills add https://github.com/prof18/feed-flow --skill run-maestro-release-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Running FeedFlow's full Maestro end-to-end release validation across Android and iOS manually is slow and error-prone, and scattered logs make it hard to see which flows failed and why. This Skill automates the entire release gate and produces consolidated reports with failure classifications.

Core Features & Use Cases

  • Full release gate execution: Builds, installs, pushes fixtures, and runs every smoke and regression Maestro flow on Android and iOS in parallel, continuing after failures to capture the complete failure set.
  • Structured reporting: Generates a visual report.html plus a terminal-friendly report.md with pass/fail counts per platform and suite, failed flow names, failure classifications, evidence lines, and links to per-flow logs.
  • Failure triage: Classifies failures into categories such as Maestro infrastructure, app crash, environment setup, permission dialogs, and timing issues to speed up diagnosis before a release.
  • Use Case: Before tagging a FeedFlow release, ask the assistant to run the full Maestro suite; it executes all flows and returns a summary of failed flows with first-pass diagnoses and log locations.

Quick Start

Ask the assistant to run the full FeedFlow Maestro release test suite and summarize any failed flows with their report locations.

Frequently Asked Questions about run-maestro-release-tests

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

FAQPage Schema
How do I run all Maestro E2E tests for Android and iOS?

Run the bundled Python script from the FeedFlow repo root with no arguments to execute every smoke and regression flow on both platforms in parallel. It builds and installs each app, pushes fixtures, runs all flows, and writes report.html and report.md under .tmp/maestro-release-tests.

How to run only Android or only smoke Maestro flows?

Pass --platform android or --platform ios to limit platforms, and --suite smoke or --suite regression to limit suites. These flags can be combined, for example a smoke-only Android pass while debugging.

What do I need installed to run Maestro release tests?

You need the maestro CLI on your PATH, a running Android device or emulator, and a booted iPhone 17 Pro simulator for iOS flows. The script generates the Xcode project automatically if iosApp/FeedFlow.xcodeproj is missing.

Why does a Maestro flow fail even though the app works?

Many failures come from infrastructure issues like device server crashes, timeouts, permission dialogs, or missing fixtures rather than app regressions. The report classifies each failure, but you should verify ambiguous cases against screenshots and UI hierarchies in ~/.maestro/tests before calling it a product bug.

Where are Maestro test reports and logs stored?

Reports and per-flow logs are written to .tmp/maestro-release-tests/<timestamp>/ in the repo, with report.html as the main visual report and report.md for terminal review. Additional Maestro artifacts like screenshots live under ~/.maestro/tests/.