go-sqlmock VS gotests

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

A huge time-saver for me when generating table-driven test boilerplate in Go has been using gotests[0] to generate the template.

If you use VSCode with the Go extension it's already available there as a command "Go: Generate Unit Tests for Function/Package".

[0] https://github.com/cweill/gotests

I believe vscode does it using gotests (https://github.com/cweill/gotests), so people can probably use it outside of vscode too.

What can do this plugin? - Modify struct tags. - Run go get, go mod & go generate commands inside of nvim. - Implement interface by impl. - Generate tests by gotests. - Install required tools for plugin working(by go install).

I was just thinking about some smart solutions. For example generating test plan and fake data by inspecting current changes on the code and db schema. Just like this https://github.com/cweill/gotests but for performance test plans.

Did you encounter gotests when you were doing your research? It's a table test generation tool that generates test code using t.Run(). I do wish it could generate tests using testify, because I frequently end up rewriting the code in the inner loop, but I still use it because it's better than I am about ensuring there's a test for all functions I write.

I use https://github.com/cweill/gotests to generate the test scaffolding.

You can save yourself a minute and generate the test case boilerplate for your with https://github.com/cweill/gotests :)