qa-testing-mobile

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

QA Mobile Testing

移动应用QA测试

Design and execute reliable, cost-aware mobile testing across iOS and Android (native + cross-platform).
针对iOS和Android(原生+跨平台)设计并执行可靠、成本可控的移动测试。

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.
  • 填写
    assets/mobile-test-plan.md
    以定义风险、测试层级和发布门禁。
  • 根据分析数据填写
    assets/device-matrix.md
    ,选择Tier 1/2/3的设备覆盖范围。
  • 使用
    references/framework-comparison.md
    选择自动化框架。
  • 使用
    references/flake-management.md
    设置测试不稳定预算、重跑规则和隔离机制。

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.
  • 定义iOS和Android全平台的移动测试策略。
  • 规划设备矩阵、系统版本覆盖和风险层级。
  • 选择自动化框架及CI+设备实验室设置方案。
  • 覆盖性能、网络/离线、后台运行和权限测试场景。
  • 定义发布前门禁、分阶段发布和应用商店上架就绪检查。

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).
  • 目标平台、支持的系统版本和设备类型。
  • 应用类型(原生、跨平台、混合/网页视图)。
  • 核心用户流程和风险区域。
  • 分发渠道和发布节奏。
  • 现有测试工具、CI和设备实验室访问权限(Firebase Test Lab、BrowserStack、AWS Device Farm)。
  • 可观测性和发布控制工具(Crashlytics/Sentry、性能/RUM、功能开关、分阶段发布)。
  • 测试数据策略(数据预填充/重置、测试账号、环境一致性)。

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.
  1. 定义质量风险和SLI指标(无崩溃率、ANR、启动时间、核心流程成功率)。
  2. 基于分析数据构建设备矩阵;PR门禁优先使用模拟器/仿真器。
  3. 选择测试框架(默认:XCUITest + Espresso/Compose;仅当能降低总成本时才引入跨平台框架)。
  4. 搭建测试层级:单元测试、集成/契约测试、UI冒烟测试、真机针对性端到端测试。
  5. 补充移动特有场景覆盖:权限、前后台切换、深度链接、离线/弱网络。
  6. 添加性能检查(启动、滚动卡顿、内存占用)和可访问性检查。
  7. 设置测试不稳定预算、重跑限制、隔离策略和故障排查机制(产物留存+可复现性)。
  8. 定义发布门禁和应用商店上架就绪标准;通过分阶段发布推送,同时配合监控与回滚机制。

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.
  • 移动测试策略和设备矩阵。
  • 自动化测试计划和框架选型方案。
  • 带优先级的测试用例清单。
  • 发布就绪检查清单。
  • CI流水线和测试报告方案。

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.
  • UI测试聚焦核心流程;保持测试套件轻量化、快速执行。
  • 区分设备特定bug与逻辑回归问题。
  • 跟踪每个测试/设备的不稳定率;隔离并修复高频问题。
  • 验证权限、通知和后台行为。
  • 优先使用稳定选择器(可访问性ID/测试标签),而非本地化文本。

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.
  • assets/device-matrix.md
    :用于系统版本和设备覆盖规划。
  • assets/mobile-test-plan.md
    :用于测试范围和自动化规划。
  • assets/release-readiness-checklist.md
    :用于发布门禁检查。

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.
  • references/framework-comparison.md
    :用于XCUITest、Espresso/Compose、Appium、Detox、Maestro和Flutter测试框架的选型对比。
  • references/flake-management.md
    :用于测试不稳定问题的治理指导。
  • data/sources.json
    :精选文档和设备实验室链接集合。

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.
  • 如需iOS专项测试深度指导,使用qa-testing-ios(XCTest、Swift Testing、simctl)。
  • 如需Android专项测试深度指导,使用qa-testing-android(Espresso、Compose Testing、UIAutomator)。
  • 如需网页和网页视图测试,使用qa-testing-playwright
  • 如需移动架构指导,使用software-mobile