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. Overview
JUnit 5 provides multiple methods for registering extensions. For an overview of some of these methods, refer to our Guide to JUnit 5 Extensions.
In this quick tutorial, weβll focus on programmatic registration of JUnit 5 extensions, using the @RegisterExtension annotation.
2. @RegisterExtension
We can apply this annotation to fields in test classes. One advantage of this method is that we can access the extension as an object in the test content directly.
JUnit will call the extension methods at appropriate stages.
For example, if an extension implements BeforeEachCallback, JUnit will call its corresponding interface methods before executing a test method.
3. Using @RegisterExtension With Static Fields
When used with static fields, JUnit will apply the methods of this extension after the class-level @ExtendWith based extensions have been applied.
Also, JUnit will invoke both class-level and method-level callbacks of the extension.
For example, the following extension features both a beforeAll and a beforeEach implementation:
public class LoggingExtension implements
BeforeAllCallback, BeforeEachCallback {
// logger, constructor etc
@Override
public void beforeAll(ExtensionContext extensionContext)
throws Exception {
logger.info("Type {} In beforeAll : {}",
type, extensionContext.getDisplayName());
}
@Override
public void beforeEach(ExtensionContext extensionContext) throws Exception {
logger.info("Type {} In beforeEach : {}",
type, extensionContext.getDisplayName());
}
public String getType() {
return type;
}
}
Letβs apply this extension to a static field of a test:
public class RegisterExtensionTest {
@RegisterExtension
static LoggingExtension staticExtension = new LoggingExtension("static version");
@Test
public void demoTest() {
// assertions
}
}
The output shows messages from both the beforeAll and beforeEach methods:
Type static version In beforeAll : RegisterExtensionTest
Type static version In beforeEach : demoTest()
4. Using @RegisterExtension With Instance Fields
If we use RegisterExtension with non-static fields, JUnit will only apply the extension after processing all TestInstancePostProcessor callbacks.
In this case, JUnit will ignore class level callbacks like beforeAll.
In the above example, letβs remove the static modifier from LoggingExtension:
@RegisterExtension
LoggingExtension instanceLevelExtension = new LoggingExtension("instance version");
Now JUnit will only invoke the beforeEach method, as seen in the output:
Type instance version In beforeEach : demoTest()
5. Conclusion
In this article, we did an overview of programmatically registering JUnit 5 extensions with @RegisterExtension.
We also covered the difference between applying the extension to static fields vs. instance fields.
