https://github.com/zonia3000/maven-docker-database-testing
Example of Maven project using Docker plugin for integration testing on real databases
https://github.com/zonia3000/maven-docker-database-testing
database docker example maven maven-plugin-example mysql postgresql testing
Last synced: 10 months ago
JSON representation
Example of Maven project using Docker plugin for integration testing on real databases
- Host: GitHub
- URL: https://github.com/zonia3000/maven-docker-database-testing
- Owner: zonia3000
- Created: 2018-08-24T21:10:10.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2018-08-24T21:14:47.000Z (over 7 years ago)
- Last Synced: 2025-02-13T23:45:21.551Z (12 months ago)
- Topics: database, docker, example, maven, maven-plugin-example, mysql, postgresql, testing
- Language: Java
- Size: 4.88 KB
- Stars: 2
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Example of Maven project using Docker plugin for integration testing on real databases
When you test applications performing queries on a database, it's not always possible to rely on mocks or embedded databases (e.g. H2): sometimes you need to execute the application in an environment as similar as possible to the production one. In this situations using Docker could be a good idea.
This example shows a Maven project using the [docker-maven-plugin](https://github.com/fabric8io/docker-maven-plugin) for testing a SQL query both on MariaDB and PostgreSQL databases.
## How it works
During the `pre-integration-test` phase the plugin starts 2 Docker images (one for MariaDB and one for PostgreSQL).
Inside the `src/test/docker` directory there are 2 SQL files used to create an example table on both databases. The plugin copies these files in the `docker-entrypoint-initdb.d` directory inside each Docker image. This directory is used by [both](https://hub.docker.com/_/mariadb/) [images](https://hub.docker.com/_/postgres/) for performing custom initialization.
The plugin is also configured to wait until the databases are up and running (listening on their default ports).
The plugin sets the IP address of the running image inside a Maven property having the following format: `docker.container..ip`. In this way it is possible to fill the configuration files inside the `src/test/resources` directory using Maven properties filtering. Thus, it is possible to read the proper connection configuration from the `IntegrationTest` class.
Please, have a look to the pom.xml and the other files: there are some additional tips and information contained in the comments.
## How to debug the integration test
mvn -Dmaven.failsafe.debug verify