Uploading Apps (APK & IPA)

How to upload Android APK and iOS IPA files to ContextQA, manage app versions, and reference uploaded builds in test cases and test plans.

Who is this for? SDETs and QA managers who need to upload Android APK or iOS IPA files to ContextQA before running mobile tests on the device farm.

ContextQA stores your app binaries centrally in the Uploads section of Test Development. Once uploaded, an app build can be referenced by any test case or test plan in the workspace — there is no need to re-upload the same binary for each test.

Supported File Types

File Type	Platform	Notes
.apk	Android	Universal APK; App Bundles (.aab) are not supported directly
.ipa	iOS	Ad-hoc or enterprise signed; App Store IPAs will not install

In addition to mobile app files, the Uploads section also accepts Excel documents (.xlsx, .xls) for data-driven testing. The platform auto-detects the file type on upload.

Upload Workflow

Step 1 — Navigate to Uploads

Go to Test Development from the main workspace navigation, then click on the Uploads tab. This section displays all previously uploaded files alongside their type and upload date.

Step 2 — Initiate the Upload

Click the Upload button in the top-right area of the Uploads section. A file picker dialog opens.

Step 3 — Select Your File

Choose your .apk or .ipa file from your local filesystem. The platform accepts a single file per upload operation.

Step 4 — Rename the File (Optional)

Before confirming, you can rename the file to something descriptive. Using a name that includes the app name and version makes it easier to manage multiple builds over time. For example: clinic-app-v2.4.1-debug.apk or myapp-adhoc-20250315.ipa.

Step 5 — Confirm the Upload

Click Upload to complete the process. ContextQA:

1. Validates the file extension and structure

2. Auto-detects the platform type (Android or iOS) and displays it alongside the entry

3. Stores the file securely in the workspace's storage

The uploaded file appears immediately in the Uploads list.

File Size Limits

ContextQA supports app binaries up to 500 MB per upload. If your binary exceeds this limit:

• For Android: Use ProGuard/R8 to shrink the APK, or produce a size-optimized APK from an App Bundle using bundletool with a specific ABI filter

• For iOS: Strip unused architectures and assets before packaging the IPA

Using an Uploaded App in a Test Case

When creating or executing a mobile test case, a device configuration dialog prompts you to select the app build:

1. In the device configuration panel, open the App Build dropdown.

2. Select the app by the name you gave it during upload.

3. The platform will install that specific binary on the selected device before test execution begins.

Using an Uploaded App in a Test Plan

When adding a device configuration to a test plan, the same App Build dropdown appears in the machine/device setup dialog. Each device entry in a test plan can reference a different app build — for example, you might run an older build on one device configuration and the latest build on another.

Managing Uploaded App Versions

Viewing Uploads

All uploads are listed in Test Development → Uploads with their file name, type, and upload date. There is no built-in version grouping — use clear naming conventions (include version numbers and dates in file names) to keep builds identifiable.

Copying the App Reference

After upload, click the Copy icon next to an app entry to copy its reference identifier. This identifier can be pasted into environment configuration or shared with team members who need to reference the same build.

Deleting an Upload

To remove an app build, select it in the Uploads list and use the delete action. Exercise caution: deleting a build that is currently referenced by an active test case or test plan will cause those tests to fail at execution time when the platform attempts to install the app.

Before deleting an old build, confirm that no currently active test plans or scheduled runs reference it. Replace references with a newer build first, then delete the old one.

Referencing Uploads via MCP

You can query the list of available uploads programmatically using the ContextQA MCP server. The get_test_cases and get_environments tools provide context on how builds are associated. For device and build selection during programmatic test execution:

# MCP tool call — list available test devices to match with an uploaded build
get_test_devices(query="android")

# MCP tool call — execute a test case (device + app build are configured on the test case itself)
execute_test_case(test_case_id=1234)

When executing test plans programmatically, the device and app build configuration is stored on the test plan object and applied automatically:

# MCP tool call — run a test plan (device configurations, including app builds, are pre-set)
execute_test_plan(test_plan_id=56)

Next Steps

With your app binary uploaded, you are ready to create test cases that target it. See Creating Mobile Tests for the full test creation and execution workflow.

Test iOS and Android in parallel — same workflow as web. Book a Demo → — See ContextQA automate mobile testing for your iOS and Android apps.