Testing
visionOS testing requires new mental models for input (eyes + hands, no touchscreen), space (3D window placement, volumes, immersive spaces), and audio (spatial positioning matters). Run unit and integration tests in the simulator for fast iteration. Device testing is mandatory for eye tracking accuracy, spatial audio presence, and real comfort validation.
Testing
Detox and Appium are the two dominant mobile E2E testing frameworks, but they take fundamentally different approaches. Detox is a gray-box framework purpose-built for React Native — fast and reliable but React Native only. Appium is a black-box framework that works with any mobile app on any platform
Testing
Detox is a gray-box end-to-end testing framework for React Native that synchronizes test execution with your app's internal state — eliminating the sleep() calls and timing hacks that make black-box tests brittle. This guide covers the architecture that makes Detox work and walks you through
React Native
A hands-on guide to Detox E2E testing in React Native, covering project setup, device and element APIs, synchronization with async operations, and running Detox in CI environments like GitHub Actions. Detox is the industry-standard end-to-end testing framework for React Native. Unlike Jest + RNTL which runs in
Testing
Running Detox tests in CI requires matching simulator/emulator availability to your runner OS, caching dependencies, and handling the slow parts (app builds, simulator boot) efficiently. This guide covers complete CI configurations for GitHub Actions and GitLab CI for both iOS and Android. Key Takeaways * iOS requires macOS runners — this
Testing
Flaky Detox tests almost always come from one of three sources: broken synchronization (the app isn't idle when Detox thinks it is), poor test isolation (state from one test bleeds into the next), or incorrect element selectors (the testID you're targeting doesn't exist in
React Native
A comprehensive walkthrough of React Native Testing Library with Jest, covering renderHook for custom hooks, userEvent for realistic interactions, the full query API, async utilities, and accessibility-first testing patterns. React Native Testing Library (RNTL) has matured into the standard way to test React Native components and hooks. Paired with
React Native
Snapshot testing in React Native can catch unintended UI regressions, but done wrong it becomes a rubber-stamp exercise. This post covers when snapshots add value, how to write focused inline snapshots, and patterns that keep your snapshot suite meaningful over time. Snapshot testing is one of the most misused
React Native
Testing navigation in React Native requires mocking React Navigation's hooks and prop injection, verifying that screens navigate correctly in response to user actions, and testing deep links and complex stack flows. This post covers the full range of navigation testing patterns. Navigation is one of the trickiest parts
Testing
OpenXR was designed to solve the platform fragmentation problem in XR — one API, every headset. In practice, it shifts the problem rather than eliminating it.
Testing
Android instrumentation tests run on a real device or emulator. That means every test suite invocation involves booting an emulator, installing an APK, and waiting for the Android runtime to execute your code. A test suite that takes 20 seconds on a laptop can take 10 minutes in CI. Robolectric
React Native
A deep dive into mocking native modules in React Native Jest tests, covering inline jest.mock patterns, the mocks directory, NativeEventEmitter simulation, and writing robust manual mocks for complex native APIs like Camera, Location, and Bluetooth. Native modules are the bridge between JavaScript and platform APIs like the camera, GPS,