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'll explore how to use abstraction in Ruby 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 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 Ruby, abstractions can be achieved through dynamic typing, modules, and mixins. By programming with these abstractions, 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 with a module or a class implementing an interface, you can 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 Ruby to demonstrate dependency management. This abstraction will define a method log, which our UserManager will use:

module Logger
  def log(message)
    raise NotImplementedError, 'Log method must be implemented'
  end
end

The Logger module acts as an interface, requiring any class including it to implement the log method. This simplicity highlights the ease of creating stubs or mocks for logging during tests without invoking an actual logging mechanism.

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

class UserManager
  def initialize(logger)
    @logger = logger
    @users = []
  end

  def add_user(username)
    @logger.log("User #{username} added")
    @users << username
  end

  def get_users
    @users
  end
end

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