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 does Detox's `by.id()`, `by.text()`, and `by.type()` matcher variety let you do when multiple similar elements exist on screen?
Questions in this quiz
What does Detox's `by.id()`, `by.text()`, and `by.type()` matcher variety let you do when multiple similar elements exist on screen?
What does running `detox test -c ios.sim.debug` (a Detox CLI command with a configuration name) actually do?
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 does Detox's `expect(element(...)).toBeVisible()` actually verify, versus `toExist()`?
Why does Detox require the app under test to be built in a special "test" configuration rather than testing the regular production build directly?
What is the purpose of Detox's `waitFor(...).toBeVisible().withTimeout(ms)` pattern, given that Detox already has automatic synchronization?
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 is Detox?
What is Detox's automatic synchronization feature, and what problem does it solve?
How does Detox typically integrate with a CI pipeline for React Native apps?