Discover the new @MockitoSpyBean and how it replaces the old @SpyBean in Mockito.

Baeldung offers insights into Java development, Spring framework, and software architecture, providing tutorials, articles, and best practices for mastering Java programming language and its ecosystem. By exploring Baeldung's curated content, developers can learn about Spring Boot, Hibernate, RESTful APIs, and microservices architecture for building robust and scalable Java applications. Whether you're a Java beginner or an experienced developer, Baeldung offers resources to deepen your understanding of Java development and stay updated with industry best practices.

Baeldung

Spring Framework 6.2 introduces @MockitoSpyBean as a modern replacement for the legacy @SpyBean annotation. Unlike its predecessor which creates a new spy instance and replaces the original bean, @MockitoSpyBean wraps the existing bean from the application context, preserving its lifecycle, dependencies, and proxy chain. This makes it more reliable for integration testing, especially with AOP and transactional beans. The migration is straightforward - simply replace @SpyBean with @MockitoSpyBean in existing tests. The new annotation is part of Spring's effort to provide tighter Mockito integration and is recommended for all new projects.

What is @MockitoSpyBean in Spring