> 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/mobile-testing.md).

# Mobile Testing Overview

{% hint style="info" %}
**Who is this for?** QA engineers, SDETs, and test leads who create and run Android or iOS tests in ContextQA.
{% endhint %}

## Quick answer

ContextQA mobile testing follows four stages:

[Watch the mobile testing overview](https://drive.google.com/file/d/1wAtefl0InGTTJ3Gq5qPckIBvkwCZo3uh/preview).

1. Add an Android **APK** or iOS **IPA** in **Uploads**.
2. Create a test case and select **Mobile** as the target platform.
3. Choose the platform, device, and uploaded app build.
4. Generate and execute the test, then review its result evidence.

The same mobile test cases can be grouped into a **Mobile** test suite and added to a test plan for repeatable or scheduled execution.

## Mobile testing workflow

| Stage               | Where                          | Outcome                                                      |
| ------------------- | ------------------------------ | ------------------------------------------------------------ |
| Prepare the build   | **Uploads**                    | An APK or IPA is available as an app build                   |
| Create the test     | **Test Cases → New Test Case** | A reusable mobile test case                                  |
| Configure execution | Mobile configuration step      | Platform, device, and app build are selected                 |
| Organize regression | **Plans**                      | Mobile cases are grouped into suites and plans               |
| Review evidence     | Test result or plan report     | Status, step details, screenshots, logs, and available video |

## Android and iOS at a glance

| Platform | Build type | Select during execution             |
| -------- | ---------- | ----------------------------------- |
| Android  | `.apk`     | Android device and an APK app build |
| iOS      | `.ipa`     | iOS device and an IPA app build     |

Obtain a test-installable build from your mobile engineering team. Signing and device compatibility requirements depend on how your organization builds and distributes the application.

## How mobile tests differ from browser tests

| Browser test                  | Mobile test                                              |
| ----------------------------- | -------------------------------------------------------- |
| Starts from a target URL      | Starts from an uploaded app build                        |
| Selects a browser or viewport | Selects Android/iOS and a device                         |
| Uses browser interactions     | Uses mobile actions such as tap, type, swipe, and scroll |

## Navigation

* **Uploads** — create an APK or IPA folder and manage its build.
* **Test Cases** — create, filter, edit, and run mobile tests.
* **Plans → Test Suites** — group related mobile cases.
* **Plans → Test Plans** — select suites, machines/devices, settings, and schedules.

## Recommended learning path

1. [Check the prerequisites](/mobile-testing/prerequisites.md).
2. [Upload an APK or IPA](/mobile-testing/uploading-apps.md).
3. [Create and run a mobile test](/mobile-testing/creating-mobile-tests.md).
4. Follow [Your first mobile test](/mobile-testing/mobile-testing-tutorial.md) for a complete example.
5. [Organize mobile suites and plans](/mobile-testing/mobile-test-plans.md).

## Frequently asked questions

<details>

<summary>Does ContextQA support both Android and iOS?</summary>

Yes. The verified platform selector provides **Android** and **iOS** options. Upload an APK for Android or an IPA for iOS.

</details>

<details>

<summary>Why is the App Build field empty?</summary>

The selected platform must have a compatible completed upload. Go to **Uploads**, confirm that the APK or IPA appears with **Completed** status, and then reopen the mobile configuration step.

</details>

<details>

<summary>Can I organize mobile and browser tests separately?</summary>

Yes. Test cases display their type, and test suites have a **Select Target Platform** setting. Choose **Mobile** when creating a mobile-only suite.

</details>

## See mobile testing with your own app

Bring a test-installable APK or IPA and one important mobile journey. The ContextQA team can show how build selection, device configuration, AI-assisted creation, execution, and evidence work for that journey.

[**Book a Demo →**](https://contextqa.com/book-a-demo/)


---

# 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/mobile-testing.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.