> For the complete documentation index, see [llms.txt](https://docs.qapilot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qapilot.io/use-cases-and-best-practices/mobile-smoke-regression-and-release-testing.md).

# Mobile Smoke, Regression, and Release Testing

## Mobile Smoke, Regression, and Release Testing

QApilot supports repeatable mobile release validation through recorded tests, device-based execution, and detailed reports. Start with smoke coverage, then grow suites into regression coverage.

### Define the coverage

**Smoke tests** check critical paths after a build becomes available. Keep them short and focused on release-blocking journeys.

**Regression tests** check previously working behavior after changes. Organize related test cases into suites and run them through a test plan.

**Release validation** uses those results to assess the tested build. QApilot provides evidence, but teams remain responsible for release decisions.

### Build a reliable suite

1. [Record mobile test steps](/test-creation/record-mobile-test-steps.md) or author test cases for critical user journeys.
2. Group related cases into a [test suite](/test-creation/test-suite.md).
3. Create a [test plan](/execution-and-reliability/run-mobile-test-plans.md) with the app source, device, and test data.
4. Run on local or supported cloud devices.
5. Review the [execution report](/reports-security-and-release-readiness/mobile-test-execution-reports.md) before promoting the build.

### Reduce flaky mobile tests

Flaky tests often reflect unstable timing, app state, device differences, or brittle element targeting. Use QApilot features deliberately:

* Start runs from a known app state when appropriate.
* Use waits and element-based actions for dynamic screens.
* Separate Android and iOS steps when behavior differs.
* Review healed steps and update approved locators.

[AI auto-healing](/execution-and-reliability/ai-auto-healing-for-mobile-tests.md) can recover selected locator failures. It does not validate product correctness. Review the evidence and approve changes deliberately.

### Use real devices and evidence

Cloud recording and execution support Android APK and iOS IPA builds through configured device providers. Test plans can select devices and run multiple devices concurrently where available.

Enable screenshots or video when you need diagnostic evidence. Use reports to inspect outcomes, artifacts, and logs. Use [Device Metrics](/reports-security-and-release-readiness/device-metrics-for-android-test-performance.md) for supported Android performance telemetry.

For failed local runs, use [Debugging Mobile Applications on Local Devices](/mobile-testing/debugging-mobile-applications-on-local-devices.md) to inspect steps and resolve issues.

### Schedule regression coverage

Use [scheduled test plans](/execution-and-reliability/schedule-test-plans.md) for recurring coverage. Use [CI/CD](/execution-and-reliability/continuous-integration-and-deployment-ci-cd.md) when builds should trigger configured cloud test plans.

### Related documentation

* [Android and iOS Mobile Testing Quickstart](/getting-started/android-and-ios-mobile-testing-quickstart.md)
* [Cross-Platform Execution for Android and iOS](/mobile-testing/cross-platform-execution-for-android-and-ios.md)
* [Reports Dashboard](/reports-security-and-release-readiness/mobile-test-execution-reports/reports-dashboard.md)