Send your app to rehab - Testing React Native apps with Detox
summary
Claims that Detox makes React Native end-to-end tests far more stable by using gray-box synchronization (inspect network, main/render threads, animations) and runs on iOS and Android. Demo app implements a Harvest time-tracker with three screens (loading, location, hours); tests use testIDs, device.launch with permission args, a mock API server or real backend, and build via detox build + detox test. Team writes about 5–6 location tests and finds tests more reliable but still time consuming to create and maintain.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:23Warmup
- 1:58Testing
- 2:28Testing pyramid
- 3:10Why automate today
- 3:44What is Detox
- 4:20What does Detox look like
- 5:10Blackbox vs Detox
- 7:47How Detox works
- 8:25Flow of tests in Detox
- 9:50Alejandro Ortega
- 10:33Demo
- 11:25How to test
- 12:30Use cases
- 12:55Testing in Detox
- 15:00Assumptions
- 16:08Location
- 17:01Status
- 18:07How to build the app
- 20:10Backend or mock
- 22:42Jason server
- 24:00Summary
related talks
30mDetox A year in. Building it, Testing with it
24mDetox A year in. Building it, Testing with it
20mDetox A year in. Building it, Testing with it
40mReact Native is Coming – the story of hybrid mobile application testing
30mTesting & React Native"Lessons from the Battlefield"
31mDetox: Tackling the Flakiness of Mobile Automation
20mMeet my new friend: Testing
26mIntegration Testing for React Native Apps