go-integration-tests

Go integration tests with a real Postgres database use testcontainers-go to spin up a PostgreSQL container, automatically execute database migrations, and provide per-test isolation to catch real SQL bugs.

Using testcontainers-go instead of mocks validates actual database interactions and migrations against a real PostgreSQL instance, catching subtle SQL bugs that unit tests with sqlmock might miss.

You isolate database state for each test by applying per-test database isolation, ensuring every test executes against a clean database state after running automated migrations.

To generate a Go integration test suite for your repository, you need to provide the module path, the migration directory path, and the entity or repository names as inputs to scaffold the test cases.

You should use real PostgreSQL containers over sqlmock in Go testing when you need to test database interactions and migrations accurately, automatically executing migrations before tests to catch real SQL bugs that mocks miss.