Test your Detox knowledge with a free interactive quiz — 19 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What is the basic structure of a Detox test using its matcher/action/expectation API?
Questions in this quiz
What is the basic structure of a Detox test using its matcher/action/expectation API?
What is the relationship between Detox and Appium, another popular mobile E2E testing tool?
What is Detox?
What are Detox "artifacts" (screenshots, videos, logs captured during a test run) used for?
What is a "flaky test" in the context of E2E testing, and how does Detox's design specifically aim to reduce this problem?
What is `detox.config.js` (or `.detoxrc.js`) used for?
How does Detox typically integrate with a CI pipeline for React Native apps?
Why might a test need to explicitly handle native permission dialogs (camera, location, notifications) when testing a React Native app with Detox?
Why is it generally considered bad practice to write Detox element matchers based on an element's exact screen position (coordinates) rather than testID/text/type matchers?
What is Detox's automatic synchronization feature, and what problem does it solve?
What does Detox's `by.id()`, `by.text()`, and `by.type()` matcher variety let you do when multiple similar elements exist on screen?
Why does Detox require the app under test to be built in a special "test" configuration rather than testing the regular production build directly?