Mobile QA Process

Instructions

QA for mobile is about catching what automation cannot: visual regressions across devices, real-world network conditions, store compliance, and UX friction. A working QA process is lightweight, predictable, and repeated every release.

1. QA Cadence

Tie QA to the release train, not to a calendar.

• Pre-merge: automated checks + code review (see mobile-testing-strategy).
• Pre-release candidate: smoke test on internal testing track.
• Release candidate: full regression + exploratory bug bash.
• Post-release: production smoke + monitored rollout (see staged-rollouts).

2. The Release Checklist

Every release runs the same checklist. Store it as a template in the repo.