Skip to main content

AWS Device Farm Mobile Testing with AIQ

Use AWS Device Farm when AIQ mobile testing needs coverage on real Android or iOS devices that are not available in the local lab. Treat Device Farm as an external execution environment: prepare the app build, test package, target device pool, network requirements, credentials, and expected evidence before starting the run.

When this is useful

  • Validating mobile behavior across multiple physical devices, operating system versions, or form factors.
  • Collecting device logs, screenshots, video, and performance evidence for failures that are difficult to reproduce locally.
  • Comparing AIQ mobile test results with a cloud device provider when local devices are limited.

Before running the test

  • Confirm the application build is current and signed for the target platform.
  • Confirm the test package or Appium/Selenium assets match the app version under test.
  • Use controlled test accounts and test data; do not upload production credentials or customer data.
  • Check required network allowlists, proxy settings, and access to back-end services.
  • Define the device pool intentionally instead of selecting every available device.
  • Record the AWS project, run name, app version, test package version, and device set in the test evidence.

Validation workflow

  1. Run a small smoke test first to confirm the app launches and the test framework starts correctly.
  2. Review Device Farm logs, screenshots, video, and device-level errors.
  3. Compare Device Farm failures with AIQ output and Scenario Editor assertions.
  4. Rerun only after correcting app, data, device, or environment issues identified in the evidence.

Note: AWS Device Farm changes independently from AIQ. Re-check supported platforms, frameworks, and device availability in AWS before relying on a saved configuration.

Last updated: October 5, 2026

Back to top