You've already forked testing-go-code-with-postgres
mirror of
https://github.com/xorcare/testing-go-code-with-postgres.git
synced 2025-06-30 23:23:40 +02:00
4bb736475b
In the current approach, the connection logic is only triggered at the moment of immediate need for connection. We also get a single connection opening point.
Example of testing Go code with Postgres
The example suggests a solution to the problem of cleaning the database after running tests and the problem of running tests in parallel. It also shows how to organize integration testing of Go code with Postgres.
What's interesting here?
- Example of docker-compose.yml with multiple databases and automated migrations.
- Example of test database connection management in testingpg package.
- Example of integration tests.
- And example of GitHub Actions and Gitlab CI.
How to use
Run make test-env-up test and then everything will happen by itself.
Disclaimer
This example is not an example of software architecture!