Why Snapshot testing in React Native? - Purpose & Use Cases

The Big Idea

What if your app could tell you instantly when its screen looks different than before?

The Scenario

Imagine you build a mobile app screen with many buttons, texts, and images. Every time you change something, you have to open the app and check if everything still looks right. This takes a lot of time and you might miss small mistakes.

The Problem

Manually checking UI is slow and tiring. You can easily overlook tiny changes or break parts of the screen without noticing. It's hard to keep track of all changes as your app grows bigger.

The Solution

Snapshot testing saves a picture of your UI code output automatically. When you change your code, it compares the new output to the saved snapshot. If something is different, it alerts you right away, so you can fix it fast.

Before vs After

✗ Before

render screen
open app
look carefully
hope no mistakes

✓ After

expect(renderedScreen).toMatchSnapshot();

What It Enables

Snapshot testing lets you catch UI bugs early and keep your app looking perfect without endless manual checks.

Real Life Example

When adding a new button to a screen, snapshot testing instantly shows if the button breaks the layout or changes colors unexpectedly.

Key Takeaways

Manual UI checks are slow and error-prone.

Snapshot testing automatically compares UI output to saved versions.

This helps catch visual bugs quickly and confidently.

Practice

1. What is the main purpose of snapshot testing in React Native?

easy

A. To check the app's performance speed

B. To test network requests and API responses

C. To detect unexpected changes in the UI output

D. To validate user input formats

Solution

1. Step 1: Understand snapshot testing goal

   Snapshot testing saves the UI output to detect changes later.

2. Step 2: Identify what snapshot testing checks

   It compares future UI renders to saved snapshots to catch unexpected changes.

3. Final Answer:

   To detect unexpected changes in the UI output -> Option C

4. Quick Check:

   Snapshot testing = UI change detection [OK]

Hint: Snapshot testing checks UI changes, not logic or speed [OK]

Common Mistakes:

• Confusing snapshot testing with API or performance tests
• Thinking it tests user input validation
• Assuming it measures app speed

2. Which of the following is the correct way to write a basic snapshot test in React Native using Jest?

easy

A. render().toMatchSnapshot();

B. expect(render()).toMatchSnapshot();

C. expect().toMatchSnapshot();

D. expect(render()).toBeSnapshot();

Solution

1. Step 1: Recall Jest snapshot syntax

   Jest requires wrapping the rendered output in expect() and calling toMatchSnapshot().

2. Step 2: Check each option's syntax

   expect(render()).toMatchSnapshot(); correctly wraps render output in expect() and calls toMatchSnapshot(). Others miss expect() or use wrong matcher.

3. Final Answer:

   expect(render()).toMatchSnapshot(); -> Option B

4. Quick Check:

   Use expect(render()).toMatchSnapshot() [OK]

Hint: Always wrap render output in expect() before toMatchSnapshot() [OK]

Common Mistakes:

• Omitting expect() around render output
• Using incorrect matcher like toBeSnapshot()
• Passing component directly to expect() without render

3. Given this snapshot test code:

const tree = render().toJSON();
expect(tree).toMatchSnapshot();

What will happen if the Button's title changes to "Press" in the next test run?

medium

A. The test will fail because the snapshot does not match

B. The test will pass because title changes are ignored

C. The test will throw a syntax error

D. The test will pass but log a warning

Solution

1. Step 1: Understand snapshot comparison

   Snapshots save the UI output including props like title. Changing title changes output.

2. Step 2: Effect of changing title on test

   Since the new render differs from saved snapshot, Jest will fail the test to alert the change.

3. Final Answer:

   The test will fail because the snapshot does not match -> Option A

4. Quick Check:

   Changed UI props cause snapshot test failure [OK]

Hint: Any UI change breaks snapshot test unless updated [OK]

Common Mistakes:

• Thinking snapshot ignores prop changes
• Expecting test to pass with changed UI
• Confusing snapshot failure with syntax errors

4. You wrote this snapshot test:

test('renders correctly', () => {
  const tree = render();
  expect(tree).toMatchSnapshot();
});

But Jest throws an error: expect(received).toMatchSnapshot is not a function. What is the likely cause?

medium

A. You should use toBeSnapshot() instead

B. You need to import toMatchSnapshot manually

C. The component MyComponent is missing props

D. You forgot to call .toJSON() on the render output

Solution

1. Step 1: Understand render output type

   render() returns an object, not a JSON serializable tree. toMatchSnapshot() works on JSON.

2. Step 2: Fix by calling toJSON()

   Calling toJSON() converts render output to snapshot-friendly format, enabling toMatchSnapshot() usage.

3. Final Answer:

   You forgot to call .toJSON() on the render output -> Option D

4. Quick Check:

   Call render().toJSON() before expect() [OK]

Hint: Always call .toJSON() on render output before snapshot [OK]

Common Mistakes:

• Skipping .toJSON() call on render output
• Trying to import toMatchSnapshot manually
• Using wrong matcher like toBeSnapshot()

5. You want to update your snapshot after intentionally changing your component's UI. Which command should you run to update the snapshot files?

hard

A. jest -u

B. jest --updateSnapshots

C. jest --updateSnapshot

D. jest --update-snapshots

Solution

1. Step 1: Recall Jest snapshot update command

   The correct Jest flag to update snapshots is -u or --updateSnapshot.

2. Step 2: Identify exact command

   Among options, only jest -u is the correct short form. Others are invalid or misspelled.

3. Final Answer:

   jest -u -> Option A

4. Quick Check:

   Use jest -u to update snapshots [OK]

Hint: Use jest -u to update snapshots after UI changes [OK]

Common Mistakes:

• Typing incorrect or misspelled flags
• Trying to update snapshots without flags
• Confusing updateSnapshot with updateSnapshots