Snapshot testing in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What will this snapshot test verify?

Given this Swift snapshot test code, what UI aspect does it verify?

iOS Swift

func testButtonSnapshot() {
  let button = UIButton(frame: CGRect(x: 0, y: 0, width: 100, height: 50))
  button.setTitle("Tap me", for: .normal)
  assertSnapshot(matching: button, as: .image)
}

A It checks if the button's title is correctly set to "Tap me".

B It verifies the button's accessibility label is set.

C It tests if the button responds to taps correctly.

D It verifies the button's visual appearance matches the saved image snapshot.

💡 Hint

Snapshot tests compare the UI's look to a saved image.

Snapshot testing captures the UI component's rendered image and compares it to a stored reference image to detect visual changes.

❓ lifecycle

intermediate

When should snapshot tests be updated?

You run a snapshot test and it fails because the UI changed intentionally. What is the correct next step?

A Update the saved snapshot to the new UI image after verifying the change is expected.

B Ignore the failure and keep the old snapshot as is.

C Delete the snapshot test to avoid future failures.

D Change the UI code back to match the old snapshot without review.

💡 Hint

Snapshot tests should reflect intentional UI updates.

When UI changes are intentional, update the stored snapshot to the new correct image to keep tests valid.

🔧 Debug

advanced

Why does this snapshot test fail with a size mismatch?

This snapshot test fails with a size mismatch error. What is the most likely cause?

iOS Swift

func testLabelSnapshot() {
  let label = UILabel()
  label.text = "Hello"
  assertSnapshot(matching: label, as: .image)
}

A The label text "Hello" is too long for the snapshot.

B The label has no frame or constraints, so its size is zero when snapshot is taken.

C The snapshot library does not support UILabel components.

D The test is missing a call to set the label's accessibility identifier.

💡 Hint

UI components need a size to render properly in snapshot tests.

Without a frame or layout constraints, the label's size is zero, so the snapshot image is empty or mismatched.

🧠 Conceptual

advanced

What is a key limitation of snapshot testing?

Which of these is a main limitation of snapshot testing in mobile apps?

A It automatically fixes UI bugs without developer input.

B It requires writing complex UI interaction code.

C It cannot detect functional bugs that do not affect UI appearance.

D It replaces the need for unit tests entirely.

💡 Hint

Snapshot tests only compare how things look, not how they work.

Snapshot tests only catch visual changes; they do not test app logic or behavior.

📝 Syntax

expert

What error does this snapshot test code produce?

What error will this Swift snapshot test code produce when run?

iOS Swift

func testViewSnapshot() {
  let view = UIView()
  assertSnapshot(matching: view, as: .image)
}

A Runtime error because the view has no size and cannot render an image.

B Compile error because assertSnapshot is undefined.

C Syntax error due to missing import statement for snapshot library.

D No error; the test passes successfully.

💡 Hint

Empty views without size cannot produce valid snapshots.

The view has zero size by default, so snapshotting it produces a runtime failure or empty image error.

Practice

1. What is the main purpose of snapshot testing in iOS development?

easy

A. To save a picture of the UI and detect visual changes automatically

B. To test the app's network requests

C. To check the app's memory usage

D. To verify the app's database schema

Solution

1. Step 1: Understand snapshot testing concept

   Snapshot testing captures the UI appearance as an image to compare later.

2. Step 2: Identify the main goal

   The goal is to detect unintended visual changes early by comparing snapshots.

3. Final Answer:

   To save a picture of the UI and detect visual changes automatically -> Option A

4. Quick Check:

   Snapshot testing = UI visual comparison [OK]

Hint: Snapshot testing checks UI images for changes [OK]

Common Mistakes:

• Confusing snapshot testing with network or performance tests
• Thinking it tests app logic instead of UI appearance

2. Which of the following is the correct syntax to assert a snapshot of a SwiftUI view named MyView() using the SnapshotTesting library?

easy

A. assertSnapshot(view: MyView(), as: .text)

B. assertSnapshot(view: MyView(), type: .image)

C. assertSnapshot(MyView(), format: .image)

D. assertSnapshot(matching: MyView(), as: .image)

Solution

1. Step 1: Recall correct function signature

   The SnapshotTesting library uses assertSnapshot(matching:as:) to compare views.

2. Step 2: Match parameters

   Correct usage is assertSnapshot(matching: MyView(), as: .image) to capture image snapshot.

3. Final Answer:

   assertSnapshot(matching: MyView(), as: .image) -> Option D

4. Quick Check:

   assertSnapshot(matching: view, as: .image) [OK]

Hint: Use assertSnapshot(matching: view, as: .image) [OK]

Common Mistakes:

• Using wrong parameter labels like view: or format:
• Using .text instead of .image for UI snapshots

3. Given this SwiftUI snapshot test code snippet:

let view = Text("Hello")
assertSnapshot(matching: view, as: .image)

What will happen if the UI of Text("Hello") changes color from black to red but the snapshot is not updated?

medium

A. The test will fail because the new UI image differs from the saved snapshot

B. The test will pass because text content is the same

C. The test will crash due to color mismatch

D. The test will ignore color changes and pass

Solution

1. Step 1: Understand snapshot comparison

   Snapshot testing compares saved UI images pixel by pixel.

2. Step 2: Effect of UI color change

   Changing text color changes the image, so it no longer matches saved snapshot.

3. Final Answer:

   The test will fail because the new UI image differs from the saved snapshot -> Option A

4. Quick Check:

   UI image change = test failure [OK]

Hint: Any UI visual change causes snapshot test failure [OK]

Common Mistakes:

• Assuming content text match is enough to pass
• Thinking snapshot tests ignore color or style changes

4. You wrote this snapshot test:

assertSnapshot(matching: MyView(), as: .image)

But the test always fails with an error saying the snapshot file is missing. What is the most likely cause?

medium

A. The view MyView() is not a valid SwiftUI view

B. You forgot to record the initial snapshot before running tests

C. The assertSnapshot function is deprecated

D. The test target does not import XCTest

Solution

1. Step 1: Understand snapshot test workflow

   Snapshot tests require recording a snapshot image first to compare against.

2. Step 2: Identify missing snapshot cause

   If snapshot file is missing, it means initial snapshot was not recorded with record=true.

3. Final Answer:

   You forgot to record the initial snapshot before running tests -> Option B

4. Quick Check:

   Missing snapshot file = forgot record step [OK]

Hint: Record snapshot once before testing to avoid missing file errors [OK]

Common Mistakes:

• Assuming test fails due to view code errors
• Not knowing you must record snapshots first

5. You want to test your SwiftUI view ProfileView() on both iPhone 14 and iPad Pro screen sizes using snapshot testing. Which approach correctly tests both devices in one test function?

hard

A. Use assertSnapshot once without specifying device traits

B. Write separate test functions for each device without looping

C. Use a loop over devices and call assertSnapshot with different traits for each device

D. Test only on iPhone 14 because iPad Pro is not supported

Solution

1. Step 1: Understand device traits in snapshot testing

   You can specify device traits like size and scale to simulate different devices.

2. Step 2: Use loop to test multiple devices

   Looping over device traits and calling assertSnapshot for each covers multiple devices in one test.

3. Final Answer:

   Use a loop over devices and call assertSnapshot with different traits for each device -> Option C

4. Quick Check:

   Loop + traits = multi-device snapshot test [OK]

Hint: Loop devices with traits to test multiple screens [OK]

Common Mistakes:

• Testing only one device and missing others
• Not using traits to simulate device sizes
• Writing many separate test functions unnecessarily