Testing in Swift: Unit, Integration, E2E — Complete Guide

Introduction: Why Test Swift Applications?

Developing a quality iOS or macOS application is impossible without proper testing. The Swift ecosystem has a powerful framework XCTest that allows you to write all three levels of tests: unit, integration, and E2E. Each of these levels is responsible for its own area and helps identify errors at different stages of development.

In this article, we will break down how to properly set up and write tests for Swift applications using modern practices and tools. You will learn how different types of tests differ and get ready-made code examples that you can immediately apply in your project.

Unit Testing in Swift

Unit tests are the foundation of the testing pyramid. They check the operation of individual components (methods, classes, structures) in isolation from external dependencies.

Setting Up Unit Tests in Xcode

To create a test target in Xcode, when creating a project, simply check the "Include Tests" checkbox. If the project already exists, add a new target: File → New → Target → iOS Unit Testing Bundle.

Basic Unit Test Example

Let's look at a simple example of testing a calculator:

import XCTest

final class CalculatorTests: XCTestCase {        var calculator: Calculator!        override func setUpWithError() throws {        calculator = Calculator()    }        override func tearDownWithError() throws {        calculator = nil    }        func testAddition() {        // Given        let a = 5        let b = 3                // When        let result = calculator.add(a, b)                // Then        XCTAssertEqual(result, 8, "5 + 3 should equal 8")    }        func testDivisionByZero() {        XCTAssertThrowsError(try calculator.divide(10, 0)) { error in            XCTAssertEqual(error as? CalculatorError, CalculatorError.divisionByZero)        }    }}

Best Practices for Unit Tests

• Isolation: Each test should be independent. Use setUpWithError and tearDownWithError for setup and cleanup.
• AAA Pattern: Arrange, Act, Assert.
• One assertion per test: An ideal test checks only one behavior.
• Naming: Use descriptive names: testMethodName_WhenCondition_ExpectedResult.

Integration Testing in Swift

Integration tests check the interaction between components: working with databases, network requests, file system. Unlike unit tests, here we do not mock everything, but test real interactions.

Testing Core Data

Example of testing work with Core Data:

import XCTest@testable import MyApp

final class CoreDataIntegrationTests: XCTestCase {        var coreDataStack: CoreDataStack!        override func setUpWithError() throws {        coreDataStack = CoreDataStack(inMemory: true) // Use in-memory storage    }        func testSaveAndFetchUser() {        // Arrange        let user = User(context: coreDataStack.viewContext)        user.name = "Ivan"        user.age = 30                // Act        try? coreDataStack.viewContext.save()                let fetchRequest: NSFetchRequest<User> = User.fetchRequest()        let users = try? coreDataStack.viewContext.fetch(fetchRequest)                // Assert        XCTAssertEqual(users?.count, 1)        XCTAssertEqual(users?.first?.name, "Ivan")    }}

Testing the Network Layer

For network integration tests, use