Spring Boot测试：每个模块都有Application类是一个好主意吗？

Question

My project looks like:

myProject/
         /persistence/pom.xml
         /persistence/src/main/java/PersistenceApplication.java
         /persistence/src/main/java/**.java

         /business/pom.xml
         /business/src/main/java/BusinessApplication.java
         /business/src/main/java/**.java

         /api/pom.xml
         /api/src/main/java/ApiApplication.java
         /api/src/main/java/**.java  

api depends on business and business depends on persistence module. When run in production, ApiApplication will be the main class.

However, when running tests, I feel a requirement to add PeristenceApplication and BusinessApplication just in order to run Spring tests annotated with @SpringBootTest .

Is it really a requirement? I do not know a lot about Spring-Boot and would love to know what is the recommendation here?

How can I test my modules using @SpringBootTest but without requiring *Application.java in persistence and business module?

Thanks

Answer 1

I believe that decoupling by layer (horizontally) is outdated approach from decade ago. I believe that project shouldn't be structured "module by layer" nor "package by layer".

It should be structured "package by feature" or "module by feature" or "microservice by feature" (vertical decoupling).

With vertical decoupling, you would cover within integration test certain feature in one package/module/microservice and your consideration would be naturally gone.