We had a case internally where @SpringBootTest was not sufficient to surface some classpath issues. Notably the Spring Boot launcher jar was not on the classpath. The service also had some additional classpath issues that only appeared when launched using bazel run.
@SpringBootTest does not actually use the springboot executable jar, so is not a real test of the deployable unit.
We had a case internally where @SpringBootTest was not sufficient to surface some classpath issues. Notably the Spring Boot launcher jar was not on the classpath. The service also had some additional classpath issues that only appeared when launched using bazel run.
@SpringBootTest does not actually use the springboot executable jar, so is not a real test of the deployable unit.