Mocking Hardware Sensors

In this lesson, you will learn how to simulate GPS, camera, and accelerometer data so you can test your app’s logic without needing to physically move your phone or point your camera at objects.

Why Mock Hardware Sensors?

When you are building features that rely on hardware—like a map tracker that updates when you walk or a motion-activated camera—physical testing is slow and unreliable. You cannot easily ask your device to "pretend it is in Paris" or "simulate a sudden drop." By creating a virtual test environment, you decouple your business logic from the hardware, allowing you to trigger sensor events programmatically.

Creating a Virtual Sensor Provider

To mock a sensor, you should create an abstraction layer that sits between your component and the hardware module. Instead of importing the hardware library directly into your component, you call a "Provider" or "Service."

In your development environment, you can toggle this service to return static, controlled data instead of real-time sensor updates. Here is a simple pattern for an Accelerometer mock:

// SensorService.js
import { Accelerometer } from 'expo-sensors';

export const getSensorData = (isMocked) => {
  if (isMocked) {
    // Return fake data for testing
    return Promise.resolve({ x: 0, y: 0, z: 9.8 });
  }
  // Return real hardware data
  return Accelerometer.getAccelerometerAsync();
};

Implementing the Mock Strategy

When testing a component that relies on this data, you pass the isMocked flag as true. This allows you to write tests that assert: "When the sensor returns {x: 10}, does my UI show the 'Alert' icon?"

By injecting this "Fake Provider" during your project scaffolding, you ensure that your app's logic—how it reacts to data—is sound, even if the actual device hardware hasn't moved an inch. This pattern is essential for running automated tests in your CI/CD pipelines, as automated builders (like EAS Build) generally do not have access to real-world GPS coordinates or physical movement.

Key Takeaway: Mocking hardware sensors involves abstracting device inputs through a service layer so you can inject predictable, virtual data to test app behavior consistently.