qa-testing-mobile

# QA Mobile Testing Design and execute reliable, cost-aware mobile testing across iOS and Android (native + cross-platform). ## Quick Start - Fill `assets/mobile-test-plan.md` to define risk, layers, and gates. - Fill `assets/device-matrix.md` from analytics to pick Tier 1/2/3 coverage. - Use `references/framework-comparison.md` to choose automation frameworks. - Use `references/flake-management.md` to set a flake budget, reruns, and quarantine rules. ## Scope - Define mobile test strategy across iOS and Android. - Plan device matrix, OS coverage, and risk tiers. - Choose automation frameworks and CI + device lab setup. - Address performance, network/offline, backgrounding, and permissions. - Define pre-release gates, staged rollout, and store readiness checks. ## When NOT to Use - Platform-specific iOS test command details -> [qa-testing-ios](../qa-testing-ios/SKILL.md) - Platform-specific Android test command details -> [qa-testing-android](../qa-testing-android/SKILL.md) ## Inputs - Platforms, supported OS versions, and device targets. - App type (native, cross-platform, hybrid/webview). - Critical user flows and risk areas. - Distribution channels and release cadence. - Existing test tooling, CI, and device lab access (Firebase Test Lab, BrowserStack, AWS Device Farm). - Observability and rollout controls (Crashlytics/Sentry, performance/RUM, feature flags, staged rollout). - Test data strategy (seed/reset, test accounts, environment parity). ## Workflow 1. Def...