st.orm.spring.boot.test.DataStormTest.imports omits RepositoryAopAutoConfiguration, which storm-spring's own AutoConfiguration.imports registers. Repositories in the slice are therefore unproxied, and @Transactional/interface-level advice behave differently than in production, undercutting the slice's purpose.
Also missing: JdbcTemplateAutoConfiguration (no way to verify database state outside the ORM under test, the standard slice-test pattern) and ServiceConnectionAutoConfiguration (@ServiceConnection on a @Bean-declared container silently does nothing, while docs/spring-integration.md:671-692 advertises it).
Related packaging issues in storm-spring-boot-test-autoconfigure: it declares storm-spring-boot-starter at test scope while six of its .imports entries are non-optional:, so a consumer without the starter gets a raw ClassNotFoundException from the import selector; and junit-jupiter-api at compile scope pins the consumer's JUnit version.
st.orm.spring.boot.test.DataStormTest.importsomitsRepositoryAopAutoConfiguration, which storm-spring's ownAutoConfiguration.importsregisters. Repositories in the slice are therefore unproxied, and@Transactional/interface-level advice behave differently than in production, undercutting the slice's purpose.Also missing:
JdbcTemplateAutoConfiguration(no way to verify database state outside the ORM under test, the standard slice-test pattern) andServiceConnectionAutoConfiguration(@ServiceConnectionon a@Bean-declared container silently does nothing, whiledocs/spring-integration.md:671-692advertises it).Related packaging issues in
storm-spring-boot-test-autoconfigure: it declaresstorm-spring-boot-starterat test scope while six of its.importsentries are non-optional:, so a consumer without the starter gets a rawClassNotFoundExceptionfrom the import selector; andjunit-jupiter-apiat compile scope pins the consumer's JUnit version.