Introduction to Dependencies in Testing with Kotlin

Introduction to Dependencies in Testing with Kotlin | CodeSignal Learn

Introduction to Dependencies in Testing

Implementing the Interfaces

Before diving into the dummy implementations, let's look at the interfaces that define the contracts for the dependencies used by the EmailService . These interfaces ensure the service can work with different implementations, promoting flexibility and testability. Kotlin interface ILogger {fun log(message: String)} The ILogger interface defines the contract for logging messages, which EmailService relies on to log email-related actions. Kotlin interface IEmailSender {fun send(to: String, subject: String, body: String)} The IEmailSender interface specifies the methods required for sending emails, which EmailService uses to delegate email-sending functionality.

Join the 1M+ learners on CodeSignal

Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal

Example of Using Dummies

Let's see dummies in action by setting up tests for an EmailService application using JUnit in Kotlin. Here's how you can create an EmailServiceTest.kt file with dummies : Kotlin import org.junit.jupiter.api.BeforeEach import org.junit.jupiter.api.Test import kotlin.test.assertTrue class EmailServiceTest {private lateinit var emailService: EmailService @BeforeEach fun setUp() {emailService = EmailService(DummyLogger(), DummyEmailSender())} @Test fun shouldAcceptValidEmailParameters() {val result = emailService.sendEmail("test@example.com", "Hello", "This is a test") assertTrue(result)} // Additional tests for other cases...} import org.junit.jupiter.api.BeforeEach import org.junit.jupiter.api.Test import kotlin.test.assertTrue class EmailServiceTest {private lateinit var emailService: EmailService @BeforeEach fun setUp() {emailService = EmailService(DummyLogger(), DummyEmailSender())} @Test fun shouldAcceptValidEmailParameters() {val result = emailService.sendEmail("test@example.com", "Hello", "This is a test") assertTrue(result)} // Additional tests for other cases...} In this example: DummyLogger and DummyEmailSender act as stand-ins for real implementations. They don't have any behavior; they just satisfy the interface requirements of EmailService . By using dummies, you reduce complexity and ensure that the tests are focusing solely on the logic within EmailService . This method provides an introduction to isolating dependencies with minimal effort, setting the stage for learning about more advanced test doubles like stubs, mocks, and fakes.

Implementing the Dummy Classes

Below are the dummy classes used in the EmailServiceTest . These simple implementations satisfy the required interfaces without performing any real actions. Kotlin class DummyLogger : ILogger {override fun log(message: String) {// Do nothing}} class DummyLogger : ILogger {override fun log(message: String) {// Do nothing}} The DummyLogger implements the ILogger interface but leaves the log method empty, serving only as a placeholder. Kotlin class DummyEmailSender : IEmailSender {override fun send(to: String, subject: String, body: String) {// Do nothing}} class DummyEmailSender : IEmailSender {override fun send(to: String, subject: String, body: String) {// Do nothing}} Similarly, DummyEmailSender implements IEmailSender but provides no actual functionality in the send method. It only fulfills the dependency requirements of EmailService .

Implementing the EmailService

To fully understand how dummies integrate into your testing workflow, let's look at the implementation of the EmailService that the tests are targeting. Here's how you can set up the EmailService : Kotlin class EmailService(private val logger: ILogger, private val emailSender: IEmailSender) {fun sendEmail(to: String?, subject: String?, body: String?): Boolean {if (to == null || !to.contains("@")) {return false} if (subject == null || subject.isEmpty()) {return false} if (body == null || body.isEmpty() || body.length > 1000) {return false} logger.log("Sending email to $to") emailSender.send(to, subject, body) return true}} class EmailService(private val logger: ILogger, private val emailSender: IEmailSender) {fun sendEmail(to: String?, subject: String?, body: String?): Boolean {if (to == null || !to.contains("@")) {return false} if (subject == null || subject.isEmpty()) {return false} if (body == null || body.isEmpty() || body.length > 1000) {return false} logger.log("Sending email to $to") emailSender.send(to, subject, body) return true}} This implementation outlines a basic EmailService class, using a logger and an email sender as dependencies. The method sendEmail performs basic validation checks on the email parameters and, if they're valid, logs and sends the email using the dependencies provided. By using dummies to stand in for ILogger and IEmailSender, you can isolate this email-sending logic from the complexities of actual logging and email-sending functionalities, ensuring a focused test environment.

Introduction to Dependencies in Testing with Kotlin

Introduction to Dependencies in Testing

Implementing the Interfaces

Join the 1M+ learners on CodeSignal

Example of Using Dummies

Implementing the Dummy Classes

Implementing the EmailService

Summary and Preparing for Practice