Скачать или смотреть Solving the SpringBoot+Liquibase+TestContainer Integration Test Data Population Issue

Learn how to effectively populate your database during integration tests using Spring Boot, Liquibase, and TestContainers. This guide provides clear solutions and tips for successful data integration testing.
---
This video is based on the question https://stackoverflow.com/q/74033099/ asked by the user 'Abhinash Jha' ( https://stackoverflow.com/u/4464806/ ) and on the answer https://stackoverflow.com/a/74064449/ provided by the user 'Eddú Meléndez' ( https://stackoverflow.com/u/2203890/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: SpringBoot+Liquibase+TestContainer db - not able to populate db during integration test

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Mastering Database Population in Integration Tests with Spring Boot, Liquibase, and TestContainers

In the world of software development, ensuring that your integration tests interact properly with a populated database is critical for validating application behavior. For Java developers using Spring Boot, Liquibase, and TestContainers, this can sometimes lead to challenges. A common issue seen in integration testing is the inability to populate the database with initial data when using SQL scripts. This guide will walk you through a solution to ensure your database is correctly populated during integration tests.

The Problem Statement

When setting up integration tests that rely on external databases, the goal is to have a controlled environment, where the database is maintained cleanly and seeded with specific data. In this case, a developer encountered a scenario where their SQL scripts intended to populate initial data using Liquibase were not producing the expected results during integration testing. Specifically:

The tester intended to insert data into an employee table before running the tests but found that querying the database for the expected data returned no results.

The Solution: Key Adjustments

1. Review the Application Properties

To address the issue at hand, modifying the application-test.properties file is necessary. The crucial property to change is:

[[See Video to Reveal this Text or Code Snippet]]

By setting ddl-auto to none, you ensure that Hibernate does not attempt to manage the schema, allowing Liquibase to handle all database operations. It prevents conflicts in schema creation and data population.

2. Configure Auto-Configuration for Test Database

Ensure that the configuration for the testing database is set to avoid automatic replacement by an embedded database. Modify your test class as follows:

[[See Video to Reveal this Text or Code Snippet]]

This setting will tell Spring to use the test database you're configuring instead of replacing it with an in-memory database during the tests.

3. Double-Check Your Change Log and SQL Scripts

Next, verify that your db.changelog-test-master.yaml correctly points to all necessary SQL scripts. Ensure that your scripts properly create the database schema and populate it with initial data. A sample snippet includes the commands to create a table and insert records — Ensure that the SQL files are correctly placed in the specified folder:

[[See Video to Reveal this Text or Code Snippet]]

4. Validate Your Testing Data

Finally, ensure the UUID you are querying against in your integration test matches the UUID inserted by your SQL scripts. This validation guarantees that the data you expect to retrieve is indeed present in the database.

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Integration testing with Spring Boot, Liquibase, and TestContainers can initially seem challenging, especially when it comes to database data population. By ensuring the correct configurations and validating your SQL scripts, you can streamline the testing process significantly. Following the solutions outlined above will help you effectively populate your database with controlled data for seamless integration testing. Happy coding!