Use @DynamicPropertySource instead of ApplicationContextInitializer in Junits about generator-springboot HOT 4 CLOSED

I remember changing it to use @DynamicPropertySource and reverting it back to ApplicationContextInitializer for some reason. Couldn't recollect the reason off top of my head.

Basically, I am aiming for having separate classes for Database/Localstack etc containers so that I can use them separately for specific scenarios, or use them all combined to run integration tests.

For example, if I want to run Spring Data JPA repository tests with @DataJpaTest I would like to use DBContainerInitializer. If I want to run some integration test with @SpringBootTest then I would like to use same DBContainerInitializer and LocalStackContainerInitializer without having to configure DB container for integration tests again separately.

If that can be done with @DynamicPropertiesSource then we can update it.

from generator-springboot.

I will check sharing of containers for multiple tests from different classes

from generator-springboot.

Please go through this link https://rieckpil.de/reuse-containers-with-testcontainers-for-fast-integration-tests/ it helps to use @dynamicproperties

from generator-springboot.

In order to use @DynamicPropertiesSource we need to have a base class with ALL the containers defined. It would become bulky as and when we add more containers. Also, ApplicationContextInitializers play nice when running tests parallelly as opposed to having a base class with static containers.

So, for now, let us continue with current approach.

from generator-springboot.