Prerequisites
Prepare an Android APK or iOS IPA, confirm workspace access, choose a safe test account, and verify device capacity before running a mobile test.
Last updated
Was this helpful?
Prepare an Android APK or iOS IPA, confirm workspace access, choose a safe test account, and verify device capacity before running a mobile test.
Before creating a mobile test, prepare the application build, test data, and expected device coverage.
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.
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.
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.
A useful prompt names the screen, action, input, and expected outcome:
Use environment variables or approved test data instead of placing secrets directly in the prompt.
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.
Confirm that the upload uses the matching type—APK for Android or IPA for iOS—and that its status is Completed.
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.
Next, upload the app build.
Last updated
Was this helpful?
Was this helpful?
Launch the sample app. Tap Sign in, enter the approved test account,
submit the form, and verify that the Dashboard heading is visible.