MobileHub Module
Mobile device farm for interactive and automated testing on real devices, emulators, and simulators.
MobileHub lives under the /devicer URL prefix in the application.
The product was previously called Devicer, which is why routes, API paths, and Appium capabilities still use devicer, /df/, and df: identifiers.
What You Can Do
- Browse the device fleet and filter it by platform, model, OS version, type, and status.
- Start an interactive live testing session with video streaming, touch, gestures, and keyboard input.
- Install apps from the app catalog or from an uploaded binary, and push or pull files on the device.
- Run automated Appium or WebDriver sessions and group them into builds.
- Reserve devices in advance so they are available when you need them.
- Run accessibility audits on the current screen and keep the results as a persistent report.
- Report bugs from a session straight into the issue tracker.
- Track device usage, reservations, and sessions in reports.
Session Types
| Type | Started from | What you get |
|---|---|---|
| Live | The Devices page, or an active reservation | Streaming video, full device control, artifacts, notes, accessibility audits |
| Automation | An Appium or WebDriver client, or the CLI | Session record, artifacts, build grouping, test event timeline |
Page Guide
| Page | What it covers |
|---|---|
| Dashboard | Fleet metrics, recent activity, most used devices, quota usage |
| Devices | Device catalog, filters, tree view, starting and reserving devices |
| Live Testing | The live session list and the session detail workspace |
| Device Control | Streaming, gestures, toolbar, geolocation, microphone, invitations |
| Automated Testing | Builds, automation sessions, and the test event API |
| Apps & Files | App catalog, file repository, uploads, and the upload API |
| Reservations | Scheduling devices and managing reservations |
| Issue Tracker | Reporting bugs from a session and the module issue list |
| Reports | Device usage, reservation, and session analytics |
| Accessibility | Live audits, persistent reports, findings, triage, and exports |
| Settings | API keys, config generator, session defaults, quotas |
| Appium Config | Hub URL, df: capabilities, and generated code examples |
| API Reference | Gateway prefixes and the endpoints the module uses |
Related Modules
BrowserHub, at the /browser URL prefix, reuses the MobileHub session, file, report, and settings components for desktop browser testing.
The session workspace, artifact panels, and invitation flow behave the same way there.
Bugs reported from a MobileHub session are created in the TestPilot issue tracker. See TestPilot Issue Tracker for how issues are managed after they are filed.
Permissions
Starting a session, reserving a device, joining a session, adding a device to a parallel view, and ending an active session all require the devicefarm:session:create permission.
Destructive controls on session records use devicefarm:session:delete.
Filing a bug from a session additionally requires the issue tracker's create permission.
The Device Farm backend is an external service. The controls described here are client-side affordances: cards, dialogs, and forms hide or disable actions when the permission is missing, but the exact server-side enforcement is owned by that service.
