Fleet Orchestration

Control Multiple Android Devices Simultaneously

Testing two-sided marketplaces—such as ridesharing driver vs. passenger or courier vs. customer—requires simulating multiple moving phones simultaneously. Mockery provides strictly isolated per-device simulation channels controlled from separate browser tabs.

System Topology

Independent Multi-Channel Routing

One website account controls multiple independent physical Android phones with dedicated credentials and zero crosstalk.

Browser Tab 1 (?device=1)
Driver Phone (Pixel 8)

Navigating Route A at 60 km/h along Highway 101 toward pickup zone.

Channel: user_25:cred_1
Browser Tab 2 (?device=2)
Passenger Phone (Galaxy S23)

Stationary at pickup curb coordinate (37.7749, -122.4194) waiting for driver.

Channel: user_25:cred_2
Browser Tab 3 (?device=3)
Courier Phone (Motorola G)

Simulating urban cycling route at 18 km/h completing restaurant pickup.

Channel: user_25:cred_3
Backend SimulationStateStore maintains independent route geometry, speeds, elapsed clocks, and pause states per device ID.

Multi-Device Architecture Features

Engineered for QA test labs and automated fleet testing.

🔑

Up to 100 Dedicated Device Credentials

Create unique, write-only username/password pairs for each test device in your lab. Passwords are hashed with bcrypt in MySQL and never transmitted in plaintext.

🎛️

Navbar Device Selector

Quickly switch between devices using the dropdown in Mockery Controller’s top navigation bar. Selecting a device loads its active route and marker instantly.

🛡️

Single-Controller Arbitration

If two QA testers open the same device channel, Mockery assigns CONTROLLER to the first tab and OBSERVER to the second, preventing movement ticker conflicts and jitter.

⚡

Instant Take Over Action

An observer tab displays a prominent [ Take Over ] banner. Clicking it demotes the incumbent tab and smoothly transfers the authoritative physics clock with zero simulation resets.

Setup Guide

Setting Up a 2-Device Synchronized Test

Follow these steps to test a ridesharing passenger-driver proximity workflow:

  1. Create Device Credentials: In Mockery Controller, add Device 1 named "Driver_1" and Device 2 named "Passenger_1".
  2. Configure Physical Phones: In phone A's Mockery Spoofer, enter Driver_1 credentials. In phone B, enter Passenger_1 credentials.
  3. Open Two Browser Tabs: On your workstation, open Tab 1 selecting Driver_1 and Tab 2 selecting Passenger_1.
  4. Execute Simulation: In Tab 2, set Passenger_1 stationary at a hotel entrance. In Tab 1, plot Driver_1 approaching from 2 km away at 50 km/h. Click Start!
  5. Observe Interactions: Watch both phone screens. Verify that when Driver_1 passes the 200m radius, the Passenger phone receives the "Driver is arriving" push notification.

Scale Your Multi-Device Testing Lab

Manage your device credentials and simulate synchronized multi-phone interactions with Mockery Controller.