In previous lessons, we explored the fundamentals of Test-Driven Development (TDD), the Red-Green-Refactor cycle, and the setup of a testing environment. Now, we shift our focus to a key aspect of TDD: managing dependencies. Managing dependencies ensures that each unit of your application can be tested in isolation, which is crucial in TDD for maintaining code reliability and robustness.

In this lesson, we will examine how to use abstraction in Swift to manage dependencies effectively. Using simple examples, we will demonstrate how to apply the Red-Green-Refactor cycle in this context. Let’s dive in.

Dependencies in software development refer to the components or systems that a piece of code relies on to function properly. In the context of testing, dependencies can complicate unit tests because they might introduce external factors that affect the test outcomes. To ensure tests are isolated and independent, we use abstractions.

In Swift, abstractions can be achieved through protocols. By programming against these protocols, you can easily swap out implementations, making code more modular and test-friendly.

For example, consider a logger that a component uses to record actions. By abstracting the logger through a protocol, you decouple the component from a specific logging implementation. This abstraction allows you to replace the actual logger with a mock or fake when testing, thus focusing on testing the component, not its dependencies.

We'll create a simple logger abstraction using Swift to demonstrate dependency management. This abstraction will define a method log, which our UserManager will use:

protocol Logger {
    func log(_ message: String)
}

The Logger protocol defines a single method log that accepts a message of type String. The simplicity of this abstraction highlights the ease of creating test stubs or mocks to simulate logging during tests without invoking an actual logging mechanism.

Next, we build a UserManager class by using the Logger protocol. We utilize dependency injection to pass in a logger, illustrating how to maintain independence between the UserManager and any specific logging implementation.

class UserManager {
    private let logger: Logger
    private var users: [String] = []

    init(logger: Logger) {
        self.logger = logger
    }

    func addUser(_ username: String) {
        logger.log("User \(username) added")
        users.append(username)
    }

    func getUsers() -> [String] {
        return users
    }
}

In UserManager, the logger is injected through the initializer, which allows you to provide different implementations of Logger — such as a fake for testing or a real logger for production.