In previous lessons, we've explored the fundamentals of Test Driven Development (TDD), specifically the Red-Green-Refactor cycle and setting up a robust testing environment using Kotlin and JUnit. 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 interfaces for abstraction in Kotlin, allowing us to manage dependencies effectively. Using simple examples, we will demonstrate how to apply the Red-Green-Refactor cycle in this context. We'll use Kotlin with JUnit, a widely used framework in testing, to provide practical 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.

An interface in Kotlin acts as a contract that defines the methods a class should implement. By programming against interfaces, 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 as an interface, you decouple the component from a specific logging implementation. This abstraction allows you to replace the actual logger with a mock or stub when testing, thus focusing on testing the component, not its dependencies.

We'll create a simple logger interface called Logger to demonstrate dependency management. This interface will define a method log, which our UserManager will use:

Kotlin
Copy to clipboard
1interface Logger {
2    fun log(message: String)
3}

The Logger interface defines a single function log that accepts a message of type String. The simplicity of this interface 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 using the Logger interface. We utilize dependency injection to pass in a logger, illustrating how to maintain independence between the UserManager and any specific logging implementation.

Kotlin
Copy to clipboard
1class UserManager(private val logger: Logger) {
2    private val users = mutableListOf<String>()
3
4    fun addUser(username: String) {
5        users.add(username)
6        logger.log("User $username added")
7    }
8
9    fun getUsers(): List<String> {
10        return users
11    }
12}

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

To test the UserManager without relying on a real logging mechanism, we create a MockLogger class. This mock implementation collects logged messages, enabling us to verify that the UserManager interacts with the Logger as expected.

Kotlin
Copy to clipboard
1class MockLogger : Logger {
2    private val logs = mutableListOf<String>()
3
4    override fun log(message: String) {
5        logs.add(message)
6    }
7
8    fun getLogs(): List<String> {
9        return logs
10    }
11}

The MockLogger class implements the Logger interface. It stores all log messages in a list, which can be accessed using the getLogs method. This makes it easy to verify if specific log messages were generated during the test.

Kotlin
Copy to clipboard
1import org.junit.jupiter.api.Test
2import kotlin.test.assertTrue
3import kotlin.test.assertEquals
4
5class UserManagerTest {
6
7    @Test
8    fun shouldAddUserSuccessfully() {
9        val mockLogger = MockLogger()
10        val userManager = UserManager(mockLogger)
11
12        userManager.addUser("john")
13
14        assertTrue(userManager.getUsers().contains("john"))
15    }
16
17    @Test
18    fun shouldLogMessageWhenUserIsAdded() {
19        val mockLogger = MockLogger()
20        val userManager = UserManager(mockLogger)
21
22        userManager.addUser("john")
23        assertEquals(listOf("User john added"), mockLogger.getLogs())
24    }
25}

The UserManagerTest class includes two tests:

1. shouldAddUserSuccessfully: Verifies that adding a user updates the internal user list correctly.
2. shouldLogMessageWhenUserIsAdded: Confirms that the correct log message is generated when a user is added.

By using the MockLogger, we can ensure that the UserManager behaves correctly without relying on external logging systems, keeping the tests isolated and focused.

• Red: We start by writing tests for UserManager. The first test checks if a user is added correctly, while the second test verifies that logging occurs.
• Green: Implement UserManager to pass these tests, ensuring that both the user addition and logging functionalities work as expected.
• Refactor: The current implementation is effective, although always look for opportunities to improve code readability and maintainability.

In this lesson, we covered how to manage dependencies in unit testing using interfaces and dependency injection in Kotlin. We explored the use of mock objects to isolate components during tests. Here's a recap of the key points:

• Abstract dependencies using interfaces to facilitate test isolation.
• Implement dependency injection to pass dependencies like loggers.
• Use a mock logger to simulate dependencies in unit tests.
• Always apply the TDD cycle: Red - Write a failing test, Green - Implement minimal code to pass, Refactor - Optimize the code without changing its functionality.

In the following hands-on practice sessions, you will consolidate these concepts by applying them using TDD. Continue practicing to deepen your understanding and proficiency in TDD with Kotlin and effective dependency management.