qa-testing-mobile

Mobile app testing strategy and execution for iOS and Android. Cover device matrix, automation frameworks, performance, reliability, and release gates. Use when you need cross platform mobile QA plans or mobile testing automation guidance.

⭐24stars🔀6forks📁View on GitHub🕐Updated Jan 9, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill provides a comprehensive framework for mobile app testing strategy and execution across iOS and Android platforms. It enables teams to design robust QA plans, select optimal automation frameworks like Appium or XCUITest, and establish data-driven device matrices to ensure high-performance, reliable mobile software delivery.

Use Cases

  • Developing a cross-platform mobile QA strategy for new iOS and Android application launches.
  • Selecting and implementing the right automation framework (XCUITest, Espresso, Appium, or Detox) based on app architecture.
  • Creating a prioritized device and OS coverage matrix using usage data and risk-based tiering.
  • Integrating mobile automated tests into CI/CD pipelines using cloud labs like Firebase Test Lab or BrowserStack.
  • Defining rigorous release gates and store submission readiness checklists to ensure smooth app store approvals.
nameqa-testing-mobile
descriptionMobile app testing strategy and execution for iOS and Android. Cover device matrix, automation frameworks, performance, reliability, and release gates. Use when you need cross platform mobile QA plans or mobile testing automation guidance.

QA Mobile Testing

When to Use This Skill

Use this skill when you need to:

  • Build a mobile test strategy for iOS, Android, or cross-platform apps.
  • Create a device matrix based on usage data and risk tiers.
  • Choose between automation frameworks (XCUITest, Espresso, Appium, Detox).
  • Plan CI integration with device labs (Firebase Test Lab, BrowserStack, AWS Device Farm).
  • Define release gates and store submission readiness.

Scope

  • Define mobile test strategy across iOS and Android.
  • Plan device matrix, OS coverage, and risk tiers.
  • Choose automation frameworks and CI setup.
  • Address performance, network, and offline scenarios.
  • Define release gates and store readiness checks.

Ask For Inputs

  • Platforms, supported OS versions, and device targets.
  • App type (native, cross platform, webview).
  • Critical user flows and risk areas.
  • Distribution channels and release cadence.
  • Existing test tooling, CI, and device lab access.

Workflow

  1. Define test scope and risk matrix.
  2. Select device coverage by tier and usage data.
  3. Choose automation stack (XCUITest, Espresso, Appium, Detox).
  4. Build layered tests: unit, integration, UI, smoke.
  5. Add network, offline, and battery impact checks.
  6. Define build, signing, and store submission gates.
  7. Set flake control and rerun policy.

Outputs

  • Mobile test strategy and device matrix.
  • Automation plan and framework selection.
  • Test case inventory with priorities.
  • Release readiness checklist.
  • CI pipeline and reporting plan.

Quality Checks

  • Keep UI tests focused on critical flows.
  • Separate device specific bugs from logic regressions.
  • Track flake rate and quarantine unstable tests.
  • Verify permissions, notifications, and background behavior.

Templates

  • templates/device-matrix.md for OS and device coverage.
  • templates/mobile-test-plan.md for test scope and automation.
  • templates/release-readiness-checklist.md for release gates.

Resources

  • resources/framework-comparison.md for choosing between XCUITest, Espresso, Appium, and Detox.
  • resources/flake-management.md for flake control guidance.