rieckpil

Spring Boot 4.0, released on the 20th of November 2025, brings Spring Framework 7 and introduces changes for our testing setup.

In our projects, we often rely on the OWASP Dependency-Check Maven Plugin to scan for vulnerabilities in dependencies.

Testing is the backbone of reliable Spring Boot applications.

Waiting for slow test suites to complete has become one of the most frustrating experiences in modern Spring Boot development.

Effective logging configuration is crucial for debugging Spring Boot tests, yet many developers struggle with noisy output, missed performance issues, and container startup failures.

Managing test dependencies in Spring Boot applications can be surprisingly complex, especially when we need specific versions of testing libraries or want to understand how Spring Boot coordinates various testing frameworks.

Testing web applications effectively requires more than just verifying HTTP responses.

Database migrations are essential for maintaining consistent database schemas across environments.

When working with recent versions of Java (21+) and Mockito, many developers encounter a puzzling warning message during test execution: Mockito is currently self-attaching to enable the inline-mock-maker.

In the Java ecosystem, managing dependencies effectively is crucial for building stable and maintainable applications.

When we first start working with Spring Boot applications, we often focus on building features and functionality, leaving testing as an afterthought.

Testing is a critical aspect of any Spring Boot application, but as our projects grow, so does the time required to run our test suites.

JUnit 5, also known as JUnit Jupiter (JUnit 5 = JUnit Jupiter + JUnit Platform + JUnit Vintage), brought a significant overhaul to the JUnit ecosystem.

Spring Boot has revolutionized how we build Java applications, making it easier than ever to get up and running with robust, production-ready systems.

When developing Spring Boot web applications, filters are essential for implementing cross-cutting concerns like rate limiting, authentication, or logging.