Tutorial: test driven development

Whether you like to write your tests before writing production code, or like to create the tests afterwards, IntelliJ IDEA makes it easy to create and run unit tests. In this tutorial we’re going to show how to use IntelliJ IDEA to write tests first (Test Driven Development or TDD ).

Prerequisites

This tutorial assumes the following prerequisites:

You have created a Java project in IntelliJ IDEA.
You have folders for production and test code, either created manually or from when you created the project.
You have JUnit 4 on the classpath, either by adding a test library, or adding a dependency in Gradle or Maven.
Your source and test roots are correctly configured - source roots will appear as blue folders, test folders will have a green background.
You have created the packages you want in your project.

Creating Your First Test

Given that we’re writing our tests first without necessarily having the code we’re testing available to us yet, we’ll create our first test via the project panel.

Right-click the package you want to create the test in and select New | Java Class.
Enter the test name - given we’re testing using JUnit, this will likely be [Something]Test, for example MoodAnalyserTest.
With the cursor placed somewhere inside the class’s curly braces, press Alt+Insert.
Select Test Method | JUnit 4 from the menu. This will create a test method with the default template. Fill in a name for the test, press Enter, and the cursor will end up in the method body.

You can alter the default test method template- for example, if you wish to change the start of the method name from test to should.

Writing the Test Body

It may seem counter-intuitive to write test code for classes and methods that don’t exist, but IntelliJ IDEA makes this straightforward while keeping the compiler happy. IntelliJ IDEA can create classes and methods for you if they don’t already exist.

Write your tests describing what you want to achieve, pressing Alt+Enter on any classes that don’t exist and selecting Create class. This will give you a minimum implementation that keeps the compiler happy.

As always, you can use IntelliJ IDEA’s refactoring tools to create variables to store results in, and IntelliJ IDEA will import the most appropriate classes for you, if the correct libraries are on the classpath.
Continue writing the test body, including names of methods that you need that don’t exist, again you can use Alt+Enter and select Create method to have IntelliJ IDEA create a bare skeleton method.

Running the Tests

When following a TDD approach, typically you go through a cycle of Red-Green-Refactor. You’ll run a test, see it fail (go red), implement the simplest code to make the test pass (go green), and then refactor the code so your test stays green and your code is sufficiently clean.

The first step in this cycle is to run the test and see it fail.

Given that we’ve used IntelliJ IDEA’s features to create the simplest empty implementation of the method we’re testing, we do not expect our test to pass.

From inside the test, press Ctrl+Shift+F10 to run this individual test.
The results will be shown in the run dialog. The test name will have an icon next to it - either red for an exception, or yellow for an assertion that fails. For either type of failure, a message stating what went wrong is also shown.

Implementing the Code

The next step is to make the tests pass, which means implementing the simplest thing that works.

You can navigate to the code being tested using the usual methods - clicking through on the method name, pressing Ctrl+Alt+B while the cursor is on the method name, or pressing Ctrl+Shift+T to switch between the test and the production code.
Make the change to the method to make the test pass. Often with TDD, the simplest thing that works might be hard-coding your expected value. We will see later how iterating over this process will lead to more realistic production code.
Re-run the test, using Shift+F10 to re-run the last test.
See the test pass - the icon next to the test method should go green. If it does not, make the required changes until the test passes.

Iterate

Developing code is an iterative process. When following a TDD-style approach, this is even more true. In order to drive out more complex behaviour, we add tests for other cases.

In your test class, use Alt+Insert again to create a new test method.
Pick a second test case that specifies more requirements of the method you’re testing. Remember that you can use IntelliJ IDEA’s features to create classes and methods to keep the compiler happy.
Run this second test case, showing that it fails for the correct reason.
Change the code in the method being tested to make this test pass.
Re-run both the tests by pressing Ctrl+Shift+F10 inside the test class, not inside a single method, and see that both tests now pass. If either test fails, make the changes needed to the code to ensure the tests pass.

Summary

Writing your first test in a test-first style takes a small amount of setup - creating the test class, creating the test methods, and then creating empty implementations of the code that will eventually become production code. IntelliJ IDEA automates a lot of this initial setup.

As you iterate through the process, creating tests and then making the changes required to get those tests to pass, you build up a comprehensive suite of tests for your required functionality, and the simplest solution that will meet these requirements.

Last modified: 08 March 2021