> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qa.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Mobile regression testing

> Pin a test plan to an uploaded application build instead of a preview URL.

A regression run of a mobile app uses the build you pin, not a preview URL. Upload the binary, then pass `applicationBuildShortId` on the test plan run.

## Application builds

An **application build** is an uploaded APK or zipped simulator `.app`, identified by `applicationBuildShortId` (for example `build_abc123`). A run pins that build instead of an environment URL. The same short ID works in:

* `environment.applicationBuildShortId` on [Start Run](https://docs.qa.tech/api-reference/runs/start-test-run.md)
* `applications_config` on the [Test Run Action](https://docs.qa.tech/regression-testing/github.md#test-run-action-reference)
* Change reviews that pin a PR binary — see [PR Testing for Mobile Apps](https://docs.qa.tech/pr-testing/agents/mobile.md)

Upload has three requests: get a presigned upload URL, PUT the file, then create the build record. The shared script is on [API pull request testing](https://docs.qa.tech/pr-testing/api.md#upload-the-pr-build). The [Application Builds API](https://docs.qa.tech/api-reference/application-builds.md) is the upload reference.

## Build requirements

* **Android**: debug APK or AAB from your CI build step.
* **iOS**: simulator `.app` zipped as `.zip` or `.tar.gz`. Store and device `.ipa` builds cannot run on simulators.
* **Expo / React Native managed**: generate native projects in CI with `expo prebuild` (or download an EAS preview APK) before upload. Full build steps are in [Preparing Your App Build](https://docs.qa.tech/test-features/mobile-app-testing.md#preparing-your-app-build).

## Precedence

The run override wins over the test plan **Parameters** card, which wins over the project default. Pass `applicationBuildShortId` on the run when CI built a new binary for that job. Leave Parameters on a stable environment when you only need a scheduled or manual run against a known build.

Scheduled runs and runs without an override use the build stored on that environment. To keep it current, promote each merged build with the [Update Environment](https://docs.qa.tech/api-reference/applications/update-environment.md) endpoint. See [Keep the environment on the latest merged build](https://docs.qa.tech/pr-testing/agents/mobile.md#keep-the-environment-on-the-latest-merged-build).

## Run it from CI

> [card] [GitHub](https://docs.qa.tech/regression-testing/github.md#test-a-mobile-pull-request-build)
>
> Build, upload, and run the plan with the Test Run Action.

> [card] [GitLab](https://docs.qa.tech/regression-testing/gitlab.md#mobile-build)
>
> Upload the build and call `POST /v1/run` with `applicationBuildShortId`.

> [card] [Bitrise](https://docs.qa.tech/regression-testing/bitrise.md#test-your-mobile-builds)
>
> Upload the APK or simulator app and start the plan against it.

> [card] [API](https://docs.qa.tech/regression-testing/api.md#mobile-build)
>
> Upload once, then start the plan from any CI that can call the API.

> [card] [fastlane](https://docs.qa.tech/regression-testing/fastlane.md)
>
> Add a lane that builds, uploads, and tests every new build.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.