Unit testing ViewModels in iOS Swift - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of unit testing a ViewModel in iOS development?

To verify that the ViewModel correctly processes data and business logic independently from the UI and external dependencies.

beginner

Which Swift testing framework is commonly used for unit testing ViewModels?

XCTest is the standard framework used for unit testing in Swift, including ViewModels.

intermediate

Why should dependencies of a ViewModel be mocked during unit testing?

Mocking dependencies isolates the ViewModel's logic, ensuring tests are fast, reliable, and only fail due to ViewModel issues.

intermediate

What is a common pattern to test asynchronous code in ViewModels?

Using XCTestExpectation to wait for asynchronous operations to complete before asserting results.

intermediate

How can you verify that a ViewModel updates its published properties correctly in SwiftUI?

By observing the published properties and asserting their values after triggering ViewModel actions in tests.

What does mocking a dependency in a ViewModel test help achieve?

A Isolate the ViewModel logic from external factors

B Make the app run faster in production

C Automatically generate UI components

D Replace the ViewModel with a simpler class

Mocking isolates the ViewModel logic so tests focus only on the ViewModel's behavior.

Which XCTest feature helps test asynchronous ViewModel methods?

A XCTAssertNil

B XCTAssertEqual

C XCTFail

D XCTestExpectation

XCTestExpectation waits for async code to finish before assertions.

What is a ViewModel's role in MVVM architecture?

A Manage UI layout and appearance

B Handle business logic and data for the View

C Store user preferences only

D Connect directly to the database

The ViewModel handles business logic and prepares data for the View.

When unit testing a ViewModel, what should you avoid?

A Mocking network calls

B Checking property values

C Testing UI elements directly

D Testing business logic

Unit tests for ViewModels should not test UI elements directly; that belongs to UI tests.

How do you check if a @Published property in a ViewModel changes as expected?

A Observe the property and assert its new value after an action

B Call the property directly without triggering actions

C Use print statements in the ViewModel

D Ignore property changes in tests

Observing and asserting the property after actions confirms correct updates.

Explain how you would write a unit test for a ViewModel method that fetches data asynchronously.

Think about waiting for async calls and controlling dependencies.

Describe why mocking dependencies is important when unit testing ViewModels and how it improves test quality.

Consider how external factors can cause flaky tests.