How do I install the QA Testing Mobile skill?

Run npx skillmds@latest add majiayu000/qa-testing-mobile in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is QA Testing Mobile safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with QA Testing Mobile?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is QA Testing Mobile free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published QA Testing Mobile?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

QA Testing Mobile by majiayu000 — Agent Skill

Name: QA Testing Mobile
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

QA Testing Mobile

Mobile app testing strategy and execution for iOS and Android (native + cross-platform): choose automation frameworks, define device matrix, control flakes, validate performance/reliability/accessibility, and set CI + release gates. Use when you need a mobile QA plan, device lab/CI setup, or guidance on XCUITest/Espresso/Appium/Detox/Maestro/Flutter testing.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

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.

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

Define quality risks and SLIs (crash-free, ANR, startup time, key flow success).
Build a device matrix from analytics; keep PR gates emulator/simulator-first.
Choose frameworks (default: XCUITest + Espresso/Compose; add cross-platform only when it reduces total cost).
Build test layers: unit, integration/contract, UI smoke, targeted E2E on real devices.
Add mobile-specific coverage: permissions, background/foreground, deep links, offline/poor network.
Add performance checks (startup, scrolling/jank, memory) and accessibility checks.
Set flake budget, rerun limits, quarantine policy, and failure triage (artifacts + reproducibility).
Define release gates + store readiness; ship via staged rollout with monitoring + rollback.

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; keep suites small and fast.
Separate device specific bugs from logic regressions.
Track flake rate per test/device; quarantine and fix top offenders.
Verify permissions, notifications, and background behavior.
Prefer stable selectors (accessibility IDs/test tags), not localized text.

Templates

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

Resources

references/framework-comparison.md for choosing between XCUITest, Espresso/Compose, Appium, Detox, Maestro, and Flutter testing.
references/flake-management.md for flake control guidance.
data/sources.json for curated documentation and device lab links.

Related Skills

Use qa-testing-ios for iOS specific depth (XCTest, Swift Testing, simctl).
Use qa-testing-android for Android specific depth (Espresso, Compose Testing, UIAutomator).
Use qa-testing-playwright for web and webview testing.
Use software-mobile for mobile architecture guidance.

---name: qa-testing-mobiledescription: Mobile app testing strategy and execution for iOS and Android (native + cross-platform): choose automation frameworks, define device matrix, control flakes, validate performance/reliability/accessibility, and set CI + release gates. Use when you need a mobile QA plan, device lab/CI setup, or guidance on XCUITest/Espresso/Appium/Detox/Maestro/Flutter testing.--- # 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. ## 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. Define quality risks and SLIs (crash-free, ANR, startup time, key flow success). 2. Build a device matrix from analytics; keep PR gates emulator/simulator-first. 3. Choose frameworks (default: XCUITest + Espresso/Compose; add cross-platform only when it reduces total cost). 4. Build test layers: unit, integration/contract, UI smoke, targeted E2E on real devices. 5. Add mobile-specific coverage: permissions, background/foreground, deep links, offline/poor network. 6. Add performance checks (startup, scrolling/jank, memory) and accessibility checks. 7. Set flake budget, rerun limits, quarantine policy, and failure triage (artifacts + reproducibility). 8. Define release gates + store readiness; ship via staged rollout with monitoring + rollback. ## 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; keep suites small and fast. - Separate device specific bugs from logic regressions. - Track flake rate per test/device; quarantine and fix top offenders. - Verify permissions, notifications, and background behavior. - Prefer stable selectors (accessibility IDs/test tags), not localized text. ## Templates - `assets/device-matrix.md` for OS and device coverage. - `assets/mobile-test-plan.md` for test scope and automation. - `assets/release-readiness-checklist.md` for release gates. ## Resources - `references/framework-comparison.md` for choosing between XCUITest, Espresso/Compose, Appium, Detox, Maestro, and Flutter testing. - `references/flake-management.md` for flake control guidance. - `data/sources.json` for curated documentation and device lab links. ## Related Skills - Use [qa-testing-ios](../qa-testing-ios/SKILL.md) for iOS specific depth (XCTest, Swift Testing, simctl). - Use [qa-testing-android](../qa-testing-android/SKILL.md) for Android specific depth (Espresso, Compose Testing, UIAutomator). - Use [qa-testing-playwright](../qa-testing-playwright/SKILL.md) for web and webview testing. - Use [software-mobile](../software-mobile/SKILL.md) for mobile architecture guidance.

Frequently asked questions