Agentic testing

Mobile QA

Mobile QA runs Matcha, Coldtea's testing agent, against an Android or iOS build on a cloud device.

Mobile runs execute on Appetize devices. Appetize is the runtime for mobile QA. There is no other provider.

What Matcha runs on

Each mobile run uses a device profile that pins the platform, device, and OS version. Two profiles ship today:

  • Android: Appetize Android Pixel 7 (Android 15).
  • iOS: Appetize iPhone 15 Pro Max (iOS 17).

Matcha drives the app on the device and collects evidence the same way web runs do. The final status, evidence, and any PR reporting come from the backend workflow.

Give Matcha a build

A mobile run needs an app build. Matcha accepts a build from three sources:

  • An uploaded file: an Android .apk, or an iOS Simulator app archived as .zip or .tar.gz.
  • A build link: an HTTPS URL Matcha can download the build from.
  • A GitHub Actions artifact: the fresh build from a pull request. See mobile CI artifacts.

iOS builds are iOS Simulator builds. Build with the iphonesimulator SDK and package the .app bundle as a .zip or .tar.gz. Device builds from the iphoneos SDK and .ipa files are out of scope.

For a manual upload, keep the desktop open until the file upload and the start-run request finish. After Coldtea reports the run as started or queued, the backend owns Android and iOS execution, evidence collection, the final status, and PR reporting. You can close the desktop from that point.

Signing in on mobile

A mobile run can sign in as a mobile test user, or run signed out. Mobile test users authenticate with a password, or a password plus a TOTP code. Mobile does not use SSO providers.

Watch and read a run

While a mobile run is live, Coldtea can show a read-only device frame stream so you can watch it drive the app. After it completes, you read the verdict, steps, screenshots, logs, and recording the same way as a web run. See runs and results.

On this page