Master the most popular testing framework for Java, through the Learn JUnit course:
Mocking is an essential part of unit testing, and the Mockito library makes it easy to write clean and intuitive unit tests for your Java code.
Get started with mocking and improve your application tests using our Mockito guide:
Handling concurrency in an application can be a tricky process with many potential pitfalls. A solid grasp of the fundamentals will go a long way to help minimize these issues.
Get started with understanding multi-threaded applications with our Java Concurrency guide:
Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:
Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.
But these can also be overused and fall into some common pitfalls.
To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:
Get started with Spring and Spring Boot, through the Learn Spring course:
>> LEARN SPRINGExplore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:
Yes, Spring Security can be complex, from the more advanced functionality within the Core to the deep OAuth support in the framework.
I built the security material as two full courses - Core and OAuth, to get practical with these more complex scenarios. We explore when and how to use each feature and code through it on the backing project.
You can explore the course here:
Spring Data JPA is a great way to handle the complexity of JPA with the powerful simplicity of Spring Boot.
Get started with Spring Data JPA through the guided reference course:
Refactor Java code safely β and automatically β with OpenRewrite.
Refactoring big codebases by hand is slow, risky, and easy to put off. Thatβs where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.
Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions β one for newcomers and one for experienced users. Youβll see how recipes work, how to apply them across projects, and how to modernize code with confidence.
Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.
1. Introduction
In this quick tutorial, weβll be looking at how to test if an exception is thrown and how to test if no exception is thrown using the JUnit library.
We will, of course, make sure to cover both the JUnit 4 and JUnit 5 versions.
2. JUnit 5
Letβs look at the exception-handling assertions in JUnit 5.
2.1. Assert an Exception Is Thrown
JUnit 5 Jupiter assertions API introduces the assertThrows method for asserting exceptions.
This takes the type of the expected exception and an Executable functional interface where we can pass the code under test through a lambda expression:
@Test
void whenExceptionThrown_thenAssertionSucceeds() {
Exception exception = assertThrows(NumberFormatException.class, () -> {
Integer.parseInt("1a");
});
String expectedMessage = "For input string";
String actualMessage = exception.getMessage();
assertTrue(actualMessage.contains(expectedMessage));
}
If the expected exception is thrown, assertThrows returns the exception, which enables us to also assert on the message.
Furthermore, itβs important to note that this assertion is satisfied when the enclosed code throws an exception of type NumberFormatException or any of its derived types.
This means that if we pass Exception as the expected exception type, any exception thrown will make the assertion succeed since Exception is the super-type for all exceptions.
If we change the test above to expect a RuntimeException, this will also pass:
@Test
void whenDerivedExceptionThrown_thenAssertionSucceeds() {
Exception exception = assertThrows(RuntimeException.class, () -> {
Integer.parseInt("1a");
});
String expectedMessage = "For input string";
String actualMessage = exception.getMessage();
assertTrue(actualMessage.contains(expectedMessage));
}
The assertThrows() method enables more fine-grained control for exception assertion logic because we can useit around specific parts of the code.
2.2. Assert No Exception Is Thrown
Sometimes, itβs important to ensure that a block of code or a method executes without throwing any exceptions. JUnit 5 provides an easy way to perform this check. Letβs look at an example:
@Test
void givenABlock_whenExecutes_thenEnsureNoExceptionThrown {
assertDoesNotThrow(() -> {
Integer.parseInt("100");
});
}
The assertDoesNotThrow() method executes the provided block of code. If the code block doesnβt throw an exception, the test passes. If an exception is thrown, the test fails.
2.3. Assert a Specific Type of Exception Is Not Thrown
In some cases, we might need to assert that the code doesnβt cause a particular type of exception. JUnit doesnβt provide a built-in method for it. However, we can write a custom method to handle this scenario:
First, letβs create a functional interface that allows us to generically define the interface that can be used in our custom implementation:
@FunctionalInterface
public interface Executable {
void execute() throws Exception;
}
Then, we can use this in the custom implementation to pass the desired exception class and execute the code block:
private <T extends Exception> void assertSpecificExceptionIsNotThrown(Class<T> exceptionClass, Executable executable) {
try {
executable.execute();
} catch (Exception e) {
if (exceptionClass.isInstance(e)) {
fail(e.getClass().getSimpleName() + " was thrown");
} else {
// Any other exception types are ignored and test passes!
// Logging it here for debugging purpose
LOG.info("Caught exception: " + e.getClass().getName() + ", but ignoring since it it not an instance of " + exceptionClass.getName())
}
}
}
Now, we can use this method as:
@Test
void givenASpecificExceptionType_whenBlockExecutes_thenEnsureThatExceptionIsNotThrown() {
assertSpecificExceptionIsNotThrown(IllegalArgumentException.class, () -> {
int i = 100 / 0;
});
}
This test fails if the code block throws an IllegalArgumentException or any of its subtypes. The test passes for any other type of exception or if no exception is generated. This is useful in scenarios where we need to ensure that a specific type of exception is never thrown.
3. JUnit 4
In this section, letβs look at the different exception-handling assertions in JUnit 4.
3.1. Assert Exception Is Thrown
When using JUnit 4, we can simply use the expected attribute of the @Test annotation to declare that we expect an exception to be thrown anywhere in the annotated test method.
As a result, when the test is run, it will fail if the specified exception isnβt thrown and will pass if itβs thrown:
@Test(expected = NullPointerException.class)
public void whenExceptionThrown_thenExpectationSatisfied() {
String test = null;
test.length();
}
In this example, weβve declared that weβre expecting our test code to result in a NullPointerException.
This is enough if weβre only interested in asserting that an exception is thrown.
When we need to verify some other properties of the exception, we can use the ExpectedException rule.
Letβs see an example of verifying the message property of an exception:
@Rule
public ExpectedException exceptionRule = ExpectedException.none();
@Test
public void whenExceptionThrown_thenRuleIsApplied() {
exceptionRule.expect(NumberFormatException.class);
exceptionRule.expectMessage("For input string");
Integer.parseInt("1a");
}
In the example above, weβre first declaring the ExpectedException rule. Then in our test, weβre asserting that the code that attempts to parse an Integer value will result in a NumberFormatException with the message βFor input stringβ.
3.2. Assert No Exception Is Thrown
Unlike JUnit 5, JUnit 4 doesnβt provide a built-in method to assert that no exceptions are generated from the code. However, we can implement this logic easily. Letβs look at the implementation:
private void assertNoExceptionIsThrown(Executable executable) {
try {
executable.execute();
} catch (Exception e) {
fail(e.getClass().getSimpleName() + " was thrown");
}
}
We utilized the previously created Executable functional interface to pass the code block. If any exceptions are thrown, we catch them and explicitly fail the test. Now, we can use this in the test:
@Test
public void givenABlock_whenExecuted_thenEnsureThatNoExceptionAreThrown() {
assertNoExceptionIsThrown(() -> {
int d = 100 / 10;
});
}
The test fails if any exception is thrown in the code block.
4. Conclusion
In this article, we covered asserting exceptions with both JUnit 4 and JUnit 5. We examined methods for asserting that an exception is thrown as well as ensuring that no exceptions are thrown. Additionally, we created a custom implementation to handle specific types of exceptions.
