myapp VS go-sqlmock

I would love to suggest https://github.com/learning-cloud-native-go/myapp and https://learning-cloud-native-go.github.io/ some open source side projects I am working on.

https://github.com/learning-cloud-native-go/myapp shows how to build a Dockerized RESTful API application using Go. It includes a sample RESTful APIs/ CRUD build using Go net/http with Chi router, Postgres, DB migrations, Configs via env variables, Zerolog structural logs, Validator v10, Gorm.

You need to set these env variables/ configs. https://github.com/learning-cloud-native-go/myapp/blob/main/.env

Some open source projects I am currently working on, - https://learning-cloud-native-go.github.io/ - https://github.com/learning-cloud-native-go/myapp

Checkhttps://github.com/learning-cloud-native-go/myapp

For that, I used the lib go-sqlmock. So, for example, the following snippet is part of the person/service_test.go file:

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.

I use Sqlmock for that purpose

There is a good lib for db tests https://github.com/DATA-DOG/go-sqlmock