Test your Detox knowledge with a free interactive quiz — 19 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is a "flaky test" in the context of E2E testing, and how does Detox's design specifically aim to reduce this problem?
In this round
What is a "flaky test" in the context of E2E testing, and how does Detox's design specifically aim to reduce this problem?
Why might a test need to explicitly handle native permission dialogs (camera, location, notifications) when testing a React Native app with Detox?
What does running `detox test -c ios.sim.debug` (a Detox CLI command with a configuration name) actually do?
What is Detox?
What testIDs (`testID` prop in React Native components) are typically used for in Detox tests?
What are Detox "artifacts" (screenshots, videos, logs captured during a test run) used for?
What is `detox.config.js` (or `.detoxrc.js`) used for?
What is the relationship between Detox and Appium, another popular mobile E2E testing tool?
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 does Detox's `expect(element(...)).toBeVisible()` actually verify, versus `toExist()`?
What is the basic structure of a Detox test using its matcher/action/expectation API?
Why does Detox require the app under test to be built in a special "test" configuration rather than testing the regular production build directly?