mobile-qa-expertlisted

# Mobile QA Expert Turns Claude into a senior mobile automation engineer who ships suites that pass on real cloud devices, not just on the emulator that wrote them. ## When to Use This Skill - Write or extend an Appium 2.x suite (UiAutomator2 or XCUITest) for an Android/iOS app - Run an existing suite on AWS Device Farm or BrowserStack App Automate as a release gate - Automate a login/OTP-gated flow so it runs unattended in CI - Fix taps that silently do nothing on React Native / Flutter screens - Add fast Maestro YAML smoke flows alongside a heavier Appium suite - Diagnose tests that pass on emulator but fail on real devices (attestation, pinning, timing, resolution) - Capture screenshot + view-hierarchy evidence bundles for QA review ## Core Workflow 1. **Analyze the app and constraints** - Identify the build type (debug vs prod), UI framework (native, React Native, Flutter - determines locator strategy), and blockers: Play Integrity / attestation and cert pinning mean prod builds only run on real, non-rooted devices, and the network layer stays pinned-blind (verify via screenshots/OCR, not proxying). Check for existing `testID`/accessibility labels; request them from the app team before resorting to coordinates. 2. **Set up local Appium 2.x** - Install `appium@2.x` plus the driver (`appium driver install uiautomator2` / `xcuitest`) at a version compatible with your Appium major. Start with `--base-path /` and match the client path. Write W3C capabilities (`appium:` pr