Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Spring Boot application not excluding Jdbi bean when running tests using WebFluxTest

+2
−0

I have a simple Spring Boot 3.x reactive application that exposes a RESTful API. The application uses Jdbi in the persistence layer, and the configuration for Jdbi is straightforward:

@EnableTransactionManagement
@Configuration(proxyBeanMethods = false)
@EnableJdbiRepositories(basePackages = "tld.domain.persistence")
public static class PersistenceConfig {
  @Bean
  public Jdbi jdbi(final DataSource dataSource) {
    return Jdbi.create(new SpringConnectionFactory(dataSource))
        .installPlugin(new SqlObjectPlugin())
        .setSqlLogger(new Slf4JSqlLogger());
  }
}

The issue I'm facing occurs when testing the application. I use the WebFluxTest annotation to test the layer that exposes the resources — as it avoids instantiating unrelated Spring beans. However, the jdbi bean is still being instantiated, and the application fails because there is no DataSource available in the test context.

I've tried using various ConditionalOn* annotations to try to prevent this but the application doesn't start correctly. I also attempted to isolate the configuration in an auto-configuration class, but that didn't resolve the issue either.

Does anyone have any suggestions on how to resolve this? I would prefer not to use a separate profile for testing, as that isn't a feasible solution in this case.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

0 answers

Sign up to answer this question »