Detox for E2E testing in React Native - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Detox in React Native testing?

Detox is a gray-box end-to-end testing framework for React Native apps. It automates user interactions and verifies app behavior on real devices or simulators.

intermediate

How does Detox synchronize with the app during tests?

Detox waits for the app to be idle before performing actions or assertions, ensuring tests run only when the app is ready, avoiding flaky tests.

beginner

Which command runs Detox tests on an Android emulator?

You run Detox tests on Android using: detox test -c android.emu.debug, where the config specifies the emulator and build.

beginner

What is the role of the beforeAll hook in Detox tests?

The beforeAll hook sets up the test environment, usually launching the app once before all tests run to save time.

beginner

Why is it important to use testIDs in React Native when using Detox?

TestIDs uniquely identify UI elements so Detox can find and interact with them reliably during tests.

What type of testing is Detox primarily used for?

A Integration testing

B Unit testing

C Snapshot testing

D End-to-end testing

Detox is designed for end-to-end testing, simulating real user interactions.

Which Detox command builds the app before testing?

A detox run

B detox start

C detox build

D detox launch

The detox build command compiles the app for testing.

How does Detox identify UI elements in React Native apps?

A Using element text only

B Using testID props

C Using accessibility labels only

D Using CSS selectors

Detox uses the testID prop to locate elements reliably.

What does Detox wait for before performing actions?

A App to be idle

B Network requests to finish only

C Animations to start

D User input

Detox waits for the app to be idle to avoid flaky tests.

Which testing framework is commonly used with Detox?

A Jest

B Mocha

C JUnit

D Karma

Jest is commonly used with Detox for writing test suites.

Explain how Detox ensures your React Native app is ready before running test actions.

Think about how Detox waits for the app to settle before clicking or typing.

Describe the steps to set up and run a basic Detox test on a React Native app.

Start from installation and end with running tests.

Practice

1. What is the main purpose of Detox in React Native app development?

easy

A. To build the app's backend API

B. To style the app components

C. To automate user actions and test the app end-to-end

D. To manage app state

Solution

1. Step 1: Understand Detox's role

   Detox is a testing tool that automates user interactions to check if the app works correctly from start to finish.

2. Step 2: Compare options

   Options A, B, and C relate to backend, styling, and state management, which are not Detox's purpose.

3. Final Answer:

   To automate user actions and test the app end-to-end -> Option C

4. Quick Check:

   Detox purpose = automate user actions [OK]

Hint: Detox tests the whole app flow by simulating user actions [OK]

Common Mistakes:

• Confusing Detox with styling or state tools
• Thinking Detox builds backend APIs
• Assuming Detox only tests small parts

2. Which Detox function is used to group related tests together?

easy

A. describe()

B. it()

C. expect()

D. beforeEach()

Solution

1. Step 1: Identify grouping function

   The describe() function groups related tests into a suite for better organization.

2. Step 2: Understand other functions

   it() defines individual tests, expect() makes assertions, and beforeEach() runs setup code before tests.

3. Final Answer:

   describe() -> Option A

4. Quick Check:

   Group tests = describe() [OK]

Hint: Use describe() to group tests, it() for each test [OK]

Common Mistakes:

• Using it() to group tests instead of describe()
• Confusing expect() with grouping
• Thinking beforeEach() groups tests

3. Given this Detox test snippet, what will happen?

await element(by.id('loginButton')).tap();
await expect(element(by.id('welcomeMessage'))).toBeVisible();

medium

A. The test taps the welcome message and checks if login button is visible

B. The test taps the login button and checks if the welcome message is visible

C. The test fails because tap() is called on a non-existent element

D. The test only checks visibility without any tap action

Solution

1. Step 1: Analyze the tap action

   The code taps the element with testID 'loginButton', simulating a user pressing it.

2. Step 2: Analyze the expectation

   It then checks if the element with testID 'welcomeMessage' is visible on screen.

3. Final Answer:

   The test taps the login button and checks if the welcome message is visible -> Option B

4. Quick Check:

   tap loginButton + expect welcomeMessage visible = B [OK]

Hint: Read code line by line: tap first, then check visibility [OK]

Common Mistakes:

• Mixing up which element is tapped
• Assuming tap() fails without checking element existence
• Ignoring the order of actions

4. You wrote this Detox test but it fails with "Cannot find element by id 'submitBtn'" error. What is the likely cause?

await element(by.id('submitBtn')).tap();

medium

A. You forgot to import Detox

B. The tap() function is misspelled

C. Detox does not support by.id selector

D. The app does not have a UI element with testID 'submitBtn'

Solution

1. Step 1: Understand the error message

   The error says Detox cannot find an element with testID 'submitBtn', meaning it does not exist or is not rendered.

2. Step 2: Check other options

   tap() spelling is correct, Detox supports by.id, and import errors cause different failures.

3. Final Answer:

   The app does not have a UI element with testID 'submitBtn' -> Option D

4. Quick Check:

   Element not found = missing testID in app [OK]

Hint: Check if testID matches exactly in app code [OK]

Common Mistakes:

• Assuming tap() is wrong
• Thinking Detox lacks by.id support
• Ignoring testID spelling or missing assignment

5. You want to write a Detox test that waits for a loading spinner to disappear before tapping a button with testID 'continueBtn'. Which code snippet correctly does this?

hard

A. await waitFor(element(by.id('spinner'))).toBeNotVisible().withTimeout(5000);
await element(by.id('continueBtn')).tap();

B. await element(by.id('spinner')).tap();
await element(by.id('continueBtn')).tap();

C. await expect(element(by.id('spinner'))).toBeVisible();
await element(by.id('continueBtn')).tap();

D. await element(by.id('continueBtn')).tap();
await waitFor(element(by.id('spinner'))).toBeNotVisible();

Solution

1. Step 1: Wait for spinner to disappear

   Use waitFor(...).toBeNotVisible() with a timeout to pause until spinner hides.

2. Step 2: Tap the continue button after spinner disappears

   After waiting, tap the button safely knowing the UI is ready.

3. Final Answer:

   await waitFor(element(by.id('spinner'))).toBeNotVisible().withTimeout(5000); await element(by.id('continueBtn')).tap(); -> Option A

4. Quick Check:

   Wait for spinner gone, then tap button = C [OK]

Hint: Wait for element to hide before tapping next [OK]

Common Mistakes:

• Tapping spinner instead of waiting
• Tapping button before spinner disappears
• Checking spinner visible instead of not visible