pgxmock VS pgxatomic

It's not the right call IMO to skip mocking the database connection to achieve 100% test coverage. How your app will behave in failure scenarios that are impossible to imitate during integration tests is part of the software contract. If your choice is to panic, or return an error, document that by testing that behavior. If another dev, or future you inadvertently breaks the contract, the test suite will fail. That's what you want. For unit tests against your database you should be using either go-sqlmock if testing against database/sql or pgxmock if testing against pgx. That being said, the points raised elsewhere in this thread regarding unit tests potentially hiding edge cases in terms of how an actual database will interact with your application that are not reflective of your understanding when writing mocks are 100% valid. You should do both. Unit test your app and write integration tests as well. On my team, we run integration tests using docker-compose.

For postgres only but pgxmock is similarly excellent

You can try this one: https://github.com/ysomad/pgxatomic

Hello, my name is Alex and I've implemented a simple set of wrappers for pgx transactions so that they can be used in a clean architecture, so that transactions can be managed from the application layer without abstractions flowing. I hope someone will find it useful, any criticism, questions and of course pull requests are welcome!