POC Mobile Setup Checklist

Prepare native iOS and Android apps before a Proof of Concept with QA.tech

Before a mobile Proof of Concept (POC) kickoff, verify the items below are in place. QA.tech uploads your build, configures the project, and runs the same checks during setup — app launch, backend connectivity, and login — before you start creating tests.

Testing a web app?

See the Web POC Setup Checklist for staging URLs, email whitelisting, and browser authentication.

---

Before kickoff — verify these are ready

Your team verifies	QA.tech verifies during setup
Mobile testing enabled for your org	Mobile application created
Backend mobile IPs allowlisted	App reaches staging API
Simulator .app or .apk builds and runs locally	Build uploaded and launches on emulator
Test accounts log in on staging	Login smoke test passes

---

What to verify, and effort if not ready

Work through these in order. Backend IP allowlisting usually takes the longest when IT is involved.

Priority	Verify this is in order	Effort if not ready	Details
🔴 1	Mobile testing is enabled for your organization	Minutes	Enable mobile testing
🔴 2	Your backend allows QA.tech mobile testing IPs	1–5 days (IT)	Backend network access
🟠 3	Simulator .app (iOS) or .apk (Android) is ready	Hours	App build
🟡 4	Dedicated test accounts log in on staging	Hours	Test accounts & auth
🟢 5	QA.tech project is configured with your build	Minutes	QA.tech project setup

---

1. Enable mobile testing

Mobile testing is enabled per organization. Contact support or your QA.tech contact to enable it before the POC.

---

2. Backend network access

Biggest blocker for mobile. Your app may install and launch fine, but tests fail with network errors or login failures if your API backend blocks QA.tech traffic.

Mobile tests run on cloud emulators. API calls from the app exit through a separate set of IP ranges from web testing.

Mobile testing IPs

Get the current list from Settings → Network — see the Mobile Testing IP Whitelist section. Mobile testing uses different IP ranges than web testing.

IP addresses can change. Always use the live Mobile Testing IP Whitelist in Settings — never rely on a static copy.

Add those ranges wherever your mobile backend enforces access:

• Backend firewall or security group (AWS, GCP, Azure)
• API gateway allowlist or rate-limiting rules
• VPN / zero-trust gateway (Tailscale, Cloudflare Access, Zscaler)

Forward to IT: Email pre-filled request to your IT team

Or send the request to your contact person at QA.tech, who can help coordinate with your IT team.

Your team verifies

• The app can reach your staging API from outside your corporate network
• IT has applied the mobile IP allowlist to the correct backend endpoints

QA.tech verifies during setup

• App launches on the emulator and loads past the splash screen
• Login and API-dependent flows complete without network errors

See Mobile App Testing — Network Access and IP Access.

---

3. App build

Mobile testing requires a simulator or emulator build — not an App Store or Play Store distribution build.

iOS

Build for iOS Simulator and compress the .app as .zip or .tar.gz.

xcodebuild -scheme '{scheme_name}' \
  -sdk iphonesimulator \
  -configuration Debug

Locate the .app in build/Debug-iphonesimulator/, then:

zip -r AppName.zip AppName.app

Upload the .zip (max 4 GB). App Store .ipa files are not supported.

Android

Build an APK — not an .aab bundle.

./gradlew assembleDebug

Find the APK in {module}/build/outputs/apk/. Upload the .apk (max 4 GB).

To convert an .aab to .apk, use bundletool with --mode=universal.

Tests run on cloud iOS Simulators and Android Emulators. Physical device testing is coming soon.

Full build instructions: Mobile App Testing — Preparing Your App Build.

Your team verifies

• The build installs and launches on a local simulator/emulator
• The build points at your staging backend (not production)

---

4. Test accounts & auth

Same principles as web testing:

• Create dedicated staging accounts for each role
• Verify login works on a local emulator before sharing credentials
• Share credentials with QA.tech for Configs, or send them to your contact person at QA.tech who will add them for you

If your app uses email-based auth, also complete the email whitelisting steps from the web checklist.

---

5. QA.tech project setup

QA.tech handles this during onboarding:

1. Create a mobile application

   Settings → Applications & Envs → new application → type Mobile App

2. Add an environment

   Select iOS or Android and name the environment (for example, Staging). No URL is required.

3. Upload the build

   iOS: .zip / .tar.gz with simulator .app · Android: .apk

4. Run smoke tests

   QA.tech verifies the app launches, can log in, and reaches your backend.

---

Getting help

Contact QA.tech Support or your QA.tech contact with your platform (iOS/Android), staging API URL, and how your backend is protected.