Detox A year in. Building it, Testing with it
summary
Detox claims to make mobile end-to-end tests deterministic by running a gray‑box driver inside the app and synchronizing with the main thread so actions only execute when the app is idle. It uses native drivers EarlGrey and Espresso and a JSON RPC bridge to invoke native methods from Node. Examples show production E2E versus mocked E2E with build flavors and a mock server, and report reduced flakiness, faster runs and practical CI use Detox is gray-box and deterministic.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:15Problem
- 0:35About Rotem
- 0:58Flakiness
- 2:00How unreliable
- 2:40Appium
- 3:30Blackbox
- 4:32Graybox
- 5:53How Detox works
- 6:44Native driver
- 7:46System diagram
- 9:14Testing with Detox
- 10:39Production E2E
- 12:35MultitoE
- 13:14React Native
- 16:59Continuous Deployments
related talks
24mDetox A year in. Building it, Testing with it
30mDetox A year in. Building it, Testing with it
31mDetox: Tackling the Flakiness of Mobile Automation
26mSend your app to rehab - Testing React Native apps with Detox
30mTesting & React Native"Lessons from the Battlefield"
15mChoose a Mobile Test Automation Framework That Suits Your Team
40mReact Native is Coming – the story of hybrid mobile application testing
39mTesting, Testing, 1, 2, NaN