creating-test

Creating Test

Scaffold a unit test file using Swift Testing (@Test, #expect, #require) — not XCTest.

Steps

1. Identify the class/struct to test (e.g., UserManager, HomePresenter)
2. Determine the test file location (see below)
3. Read references/swift-testing-patterns.md for assertion and async patterns
4. Create the test file with the template below
5. Add test methods for the key behaviors

File Location

Test files mirror the app's folder structure inside the unit test target, with a _Tests suffix:

App File	Test File
Managers/User/UserManager.swift	SwiftfulStarterProjectUnitTests/Managers/User/UserManager_Tests.swift
Core/Home/HomePresenter.swift	SwiftfulStarterProjectUnitTests/Core/Home/HomePresenter_Tests.swift
Managers/ABTest/Services/MockABTestService.swift	Generally not tested (it's already a mock)

Create intermediate folders as needed to match the app structure.

Template

import Testing
@testable import SwiftfulStarterProject

struct {ClassName}_Tests {

    @Test
    @MainActor
    func someMethodReturnsExpectedResult() async throws {
        // Given
        let sut = {ClassName}(service: Mock{ServiceName}Service(), logManager: nil)

        // When
        let result = await sut.someMethod()

        // Then
        #expect(result == expected)
    }
}

Key Patterns

• Use Swift Testing — @Test + #expect + #require, NOT XCTest classes
• Use structs for test containers, not classes
• @testable import SwiftfulStarterProject — gives access to internal types
• @MainActor on tests that test @MainActor types (managers, presenters) — do NOT use @MainActor on non-UI tests
• Inject mock services — test the manager/presenter in isolation, never use Prod services
• Given/When/Then comments inside each test method — do NOT put these keywords in the method name
• No test prefix needed — Swift Testing uses @Test macro instead
• Display names — @Test("Descriptive name") for human-readable failure output
• #require for preconditions — use try #require(value) to unwrap optionals and halt early instead of force-unwrapping
• Parameterize — use @Test(arguments:) instead of copy-pasting test methods that differ only in input
• Method naming: descriptive camelCase (e.g., signOutClearsUser, loadDataWithErrorSetsErrorState)
• Struct naming: _Tests suffix (e.g., UserManager_Tests)