Unit testing - how to avoid mongodb-panache client connection to mongodb instance

[Gianfelice Catini]

Hi all,

I'm unit testing my Quarkus application that is a service layer that integrates mongoDb for CRUD operations and text-based search operations.

What I'm trying to achieve is a real unit testing so I have mocked my service layer and my panache repository (I have used the repository pattern) classes.

The unit tests I wrote work fine, but when I launch them I see in the console log the mongodb client that want to connect to a mongodDB instance (I mean during the Quarkus application bootstrap).

I tryed to remove from my test configuration profile the following two properties:

• quarkus.mongodb.connection-string
  
• quarkus.mongodb.database

 but Quarkus complains about that because it expects that properties have values.

There's a way to tell Quarkus "dont try to connect to mongodb instance at bootstrap" for a specific configuration profile?

Thank you.

[tkhm]

I had the same issue before.

I added @Default annotation on my in-memory database repository(for unit testing) and also added @IfBuildProfile("prod") on my actual database connection repository.

So, when you run your unit test, in-memory repo will be loaded because unit test will use "test" profile. In other words, actual db connection(in this case, mongodb) will not be required.

[Gianfelice Catini]

Thank you for your answer. Can you please post the most significant snippets from your code? Just few lines to understand how you did it.

Did you follow a specific documentation?

I'm not using a in-memory mongoDB right now, but I'll do because I would like to test my text-based search logic against a mock db.

Thank you.

[tkhm]

My original working code is not sharable, so I made a small sample for you. I've pushed the codes on GitHub, so could you check it once, please?

https://github.com/tkhm/sandbox-java/tree/master/panache-sample/src/main/java/org/acme

I think you'll be interested in the following files:

https://github.com/tkhm/sandbox-java/blob/master/panache-sample/src/main/java/org/acme/GreetingService.java

https://github.com/tkhm/sandbox-java/blob/master/panache-sample/src/main/java/org/acme/InMemoryGreetingRepository.java

https://github.com/tkhm/sandbox-java/blob/master/panache-sample/src/main/java/org/acme/PostgresGreetingRepository.java

You're using Mongodb with Panache and I'm using Hibernate with Panache, so it is not the same but it might be some help.

note: when I tried this first time, I'm just only using GreetingModelDto.java class, but I found if I call this class in my unit test, it try to find data source and try to make a connection.(in other words, unit test will be failed if it can't make a connection to DB)

To avoid this, I made DTO for Hibernate/Panache and transform it to pojo.

ref: 

- Quarkus - Configuring Your Application https://quarkus.io/guides/config#configuration-profiles

- Quarkus - Contexts and Dependency Injection https://quarkus.io/guides/cdi-reference#enabling-beans-for-quarkus-build-profile

[Gianfelice Catini]

tkhm,

thank you for your example and I'm sorry for my late answer.

I cloned your repo few minutes ago and looking at your code I catched what you said in your previous post.

I really appreciate your help.

[Hugo Lavalle]

Hi did you see this: https://quarkus.io/guides/mongodb#testing-helpers ?

I had the same issue. I solved with:
- Add io.quarkus:quarkus-test-mongodb dependency to your pom.xml
- Add annotation @QuarkusTestResource(MongoTestResource.class) at the test class, just below @QuarkusTest

Be aware you don't have already a mongodb running on localhost:27017, flapdoodle uses the same port. MongoTestResource has 27017 hard coded. You can implement for example a MyMongoTestResource and change the port number, it worked for me.