vf-mobile-test

Mobile regression testing on an iOS simulator or Android emulator runs Maestro flows to verify runtime app behavior. The process detects available devices, boots simulators if needed, and generates timestamped JUnit reports with test artifacts.

Runtime validation on Expo or React Native builds catches failures that unit tests miss by verifying the app on active iOS simulators and Android emulators. It builds or installs missing development apps and executes Maestro flows to test actual device behavior.

To set up Maestro flows for React Native runtime validation, you need Node, a JDK, Maestro, and platform device tooling. Optionally, mobile-mcp can be configured to enable visual failure diagnosis with screenshots and log collection.

To diagnose runtime bugs visually on an Android emulator after a test failure, the skill uses mobile-mcp for visual investigation. It captures screenshots, collects logs, and documents probable causes when Maestro regression flows fail.

Pre-sprint validation for a React Native development build is best performed by running a Maestro regression on a target simulator or emulator. This provides machine-verified results with evidence for every runtime failure before the sprint begins.

An Expo app can pass build and unit tests but fail on a real device due to runtime issues undetected during compilation. Runtime validation on an active simulator or emulator executes Maestro flows to catch these specific behavioral failures.