Testing
OpenXR standardizes XR APIs across runtimes, but runtimes still differ in behavior, extension support, and performance characteristics. Test against each runtime you ship on. Use the Khronos OpenXR Conformance Test Suite for spec compliance, test input paths explicitly against each controller profile, and run your CI against the OpenXR loader
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,
Testing
Voice UI testing is conversation graph testing. Every intent is a node, every response is an edge. Test happy paths through the conversation tree, test slot validation for all entity types, test session persistence across turns, and test what happens when users say unexpected things at every state. Use ask-
Testing
AR testing combines computer vision validation with standard mobile QA. Key areas: marker detection accuracy across lighting conditions, plane detection latency and stability, occlusion correctness, ARCore/ARKit framework behavior, and performance on your actual target device range. Automated screenshot comparison catches visual regressions in AR scenes. Human testing across environments
Testing
Emulators are convenient but inadequate for mobile game testing. They don't throttle. They don't have real touch latency. They run on your development machine's GPU. A game that runs at 60 FPS in the emulator can drop to 20 FPS on a 3-year-
Testing
Mobile RTL layout testing is distinct from web RTL testing. On mobile, the OS itself flips the layout direction — constraints, gravity attributes, and flexbox-equivalent APIs all need to respond correctly. This guide focuses on automated testing of RTL layouts on iOS (XCUITest) and Android (Espresso), plus cross-platform approaches
Expo
Expo adds a layer of abstraction over React Native that requires specific testing strategies. The jest-expo preset handles most of the configuration complexity, but mocking expo-* modules, testing Expo Router's file-based navigation, and connecting Detox to the bare workflow each have their own patterns. This guide
React Native
@testing-library/react-native brings the same user-centric testing philosophy to mobile that Testing Library brought to the web. This guide covers component rendering, custom hook testing with renderHook, mocking stubborn native modules, taming async state with waitFor and findBy, and the act() gotchas that trip up even experienced
Testing
End-to-end testing for React Native apps has historically been painful. Tests were slow, brittle, and tied to specific device states that were hard to reproduce. Detox was built specifically to address these problems with a gray-box testing approach that gives your test runner insight into the app&
Security
Certificate pinning prevents man-in-the-middle attacks by restricting which certificates an app trusts. Without pinning, installing a custom CA certificate on a device is enough to intercept HTTPS traffic — the system trust store accepts it and the app never knows. With pinning, the app checks the certificate against
Testing
axe-core is the most widely deployed accessibility rules engine in the world, and it works inside Appium test suites — not just on the web. By injecting axe-core into WebView contexts within hybrid and cross-platform apps, you can run the same accessibility rules in your mobile CI pipeline