> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/mobile-testing/prerequisites.md).

# Prerequisites

## Quick answer

Prepare an Android APK or iOS IPA, confirm workspace access, choose a safe test account, and verify device capacity before running a mobile test. Use this page to understand when the capability applies, complete its user-facing workflow, and verify the expected result.

## What this page covers

Before creating a mobile test, prepare the application build, test data, and expected device coverage.

## Prerequisite checklist

* Access to the correct ContextQA workspace.
* An Android `.apk` or iOS `.ipa` that can be installed in your organization's test environment.
* Permission to add files in **Uploads** and create test cases.
* A non-production test account and fictional or approved test data.
* A concise user flow with at least one observable expected result.
* A target platform and device requirement agreed with the mobile team.

## Get a test-installable app build

Ask the mobile engineering team for a build intended for automated testing. Record:

* App name and version
* Platform: Android or iOS
* Supported OS versions and devices
* Backend environment used by the build
* Required test account or seeded data
* Any permissions, deep links, feature flags, or setup steps

Do not assume that a store-distributed build can be installed in a test device environment. Confirm signing and distribution requirements with the team that produced the build.

## Choose a safe first scenario

Start with a short, deterministic flow such as:

* Launch the app and verify the welcome screen.
* Sign in with a dedicated test account and verify the dashboard.
* Search for a known fictional record and verify the result.

Avoid production credentials, personal data, one-time codes owned by real users, and destructive operations.

## Prepare the test prompt

A useful prompt names the screen, action, input, and expected outcome:

```
Launch the sample app. Tap Sign in, enter the approved test account,
submit the form, and verify that the Dashboard heading is visible.
```

Use environment variables or approved test data instead of placing secrets directly in the prompt.

## Confirm execution capacity

The mobile configuration step shows the workspace's current **Parallel** and **Queued** counts. If capacity is busy, the run may wait before a device becomes available.

## Troubleshooting prerequisites

<details>

<summary>Why does my build not appear after I select Android or iOS?</summary>

Confirm that the upload uses the matching type—APK for Android or IPA for iOS—and that its status is **Completed**.

</details>

<details>

<summary>Which device should I choose?</summary>

Use the device and OS versions in your product's support matrix. For a first smoke test, choose one representative supported device; expand coverage in a test plan after the flow is stable.

</details>

Next, [upload the app build](/mobile-testing/uploading-apps.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learning.contextqa.com/mobile-testing/prerequisites.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.