Maestro Mobile Testing

What it does

Maestro Mobile Testing is an automated mobile end-to-end (E2E) testing framework designed for React Native applications. It uses declarative YAML files to define test steps, eliminating much of the boilerplate code typically found in other frameworks like Detox or Appium. Maestro provides automatic waiting and built-in retry logic for more stable tests, and offers a fast execution speed with minimal setup overhead.

When to use it

• Automating React Native app testing: Ideal for creating repeatable E2E test suites.
• Improving test stability: Reduce flaky tests through automatic waiting and retries.
• Rapidly building tests: Leverage the declarative YAML approach and interactive builder (Maestro Studio) to create tests quickly.
• Running tests on real devices: Utilize Maestro Cloud for testing within CI/CD pipelines without local simulators.

Key capabilities

• Declarative YAML-based tests: Define test steps in a human-readable YAML format, avoiding imperative code.
• Automatic waiting: Eliminates the need for manual sleep() calls and unreliable waits.
• Built-in retry logic: Automatically retries failed test steps to reduce flakiness.
• Fast execution: Optimized for speed with minimal setup overhead.
• Maestro Studio: An interactive tool for visually building tests.
• Sub-flows: Create reusable sequences of YAML steps for DRY (Don't Repeat Yourself) testing.
• JavaScript scripting: Utilizes a GraalJS runtime to handle HTTP calls and data manipulation within tests.
• Maestro Cloud: Enables real device testing in CI/CD environments.
• Selector Strategies: Supports both testID and text-based selectors for UI element identification, with guidance on when to use each approach.

Example prompts

While this skill doesn't directly respond to natural language prompts, users would interact with it by providing YAML configuration files or using Maestro Studio. Examples of YAML test configurations include:

• maestro test .maestro/smoke-test.yaml - Runs a specific test suite.
• maestro test --debug .maestro/smoke-test.yaml - Runs the test suite in debug mode, allowing step-by-step execution.
• maestro studio - Launches the interactive test builder interface.

Tips & gotchas

• Requires Java 17: Ensure you have OpenJDK@17 installed and JAVA_HOME properly configured.
• Selector Choice: Carefully consider whether to use testID or text selectors based on your app's localization, UI stability, and team preferences. Use testIDs for multi-language apps or dynamic content.
• TestID Naming Convention: When using testID selectors, follow the recommended naming convention: {component}-{action/type}[-{variant}].