The same model as Web, driven through Appium. Upload your build or point at a pipeline, pick a device target, run the same definitions you use everywhere else.
iOS and Android via Appium
/mobile mirrors /web — Overview, Tests, Runs, Issues, Suites, Configuration. The same test-definition library, the same run reports, the same issue triage. Tests author through the same autonomous and deterministic flows, with mobile-specific build and device controls in the create form.
Configure the app under test directly in /mobile/configuration. Upload a .ipa or .apk, or point at an existing build pipeline so each run installs the latest signed artifact. PR builds, release candidates, and production builds are all addressable as targets.
Pick the right surface per test. iOS Simulator and Android Emulator for fast local feedback. BrowserStack real-device cloud or a self-hosted Appium grid when you need the actual hardware. Pin a specific OS version, chipset, or device profile when a flow depends on it.
A built-in /api/emulator surface gives the Operator end-to-end control over Android emulators: install APKs, start / stop AVDs, query status, grab screenshots, and send tap / swipe / key events. Autoinstall picks up the latest build from a configured source. This is what lets the agent drive a live mobile test from inside a workspace.
Simulate offline, 3G, and wifi network conditions per test. For Android targets, set ADB device serial, app package, and main activity in configuration so the runner reaches the right surface immediately.
See how mobile fits the rest of Traceback.