Engineering & QA Hub

Stop Burning Fuel to Test Android Location Features

Testing location-aware Android applications in the real world is expensive, erratic, and impossible to reproduce. Mockery gives engineering teams a deterministic, browser-driven simulation harness to test geofencing triggers, movement physics, and multi-phone interactions right from their desks.

Why Real-World GPS Testing Fails QA Teams

Physical testing introduces variables that break automated test repeatability.

🚫

Zero Repeatability

Traffic lights, satellite constellation shifts, and cellular triangulation noise mean no two physical test drives follow identical trajectories or timings. Debugging a race condition becomes pure guesswork.

🏢

Office GPS Attenuation

Inside engineering offices and QA labs, reinforced concrete and low-E glass block L1 satellite signals. Phones report stale coordinates, flip between Wi-Fi APs, or drop fixes entirely.

👥

Multi-Party Coordination

Testing a delivery app requires verifying state between a customer phone, courier phone, and dispatcher. Coordinating three moving cars simultaneously for a 10-minute test is a logistical nightmare.

Developer Testing Guides

Explore dedicated methodologies for complex location-based app scenarios.

Boundary Validation

Geofencing Testing

Test circular and polygonal geofence transitions (Enter, Dwell, Exit) with millimeter precision. Verify boundary hysteresis and debounce filters without driving.

Read Geofencing Guide →

End-to-End QA

App Testing Matrix

Comprehensive testing matrix for rideshare, delivery, and fitness apps. Validate speed thresholds, permission toggles, and tunnel offline tolerance.

Read App Testing Matrix →

Lab Orchestration

Multi-Device Control

Simulate multiple phones concurrently from separate browser tabs. Provision up to 100 dedicated device channels for customer-courier sync testing.

Read Multi-Device Guide →

Android SDK Integration

Native Test Provider Architecture

Your application code requires zero SDK modifications or custom build flavors. Mockery operates strictly at the operating system layer via Android's native LocationManager test provider APIs.

// How your Android app consumes Mockery coordinates natively

val locationListener = LocationListener { location ->

val lat = location.latitude // Exactly matches Mockery simulation

val lon = location.longitude // Calculated from elapsed time & speed

val speed = location.speed // Injected in m/s matching throttle

val isMock = location.isMock // Returns true (standard Android flag)

}

locationManager.requestLocationUpdates(LocationManager.GPS_PROVIDER, 1000L, 0f, locationListener)

Standard Broadcast Receivers Your app’s GeofencingClient, FusedLocationProviderClient, and background broadcast receivers fire naturally as if physical satellites were overhead.

Honest Mock Flag Behavior Allows QA teams to test both normal behavior and mock-detection defense handlers using real stock Android OS behavior.

Accelerate Your Location QA Pipeline

Set up your test bench in under 5 minutes with the Mockery Spoofer app and browser controller.

Setup Guide for Devs → Launch GPS Controller