go-sqlmock VS GoLint

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

Actually in the early days of Go, devs were stuck to camalCase/PascalCase on variable naming. But VScode Go plugin managed by Microsoft at that time , and they suggested ID over id/ID, XML over xml/ Xml. Because VScode is free, it attached many users and using uppercase for abbreviations/ initialisms became a standard. Andhttps://github.com/golang/lint/issues/124 finalized it. But , still I think it is a wrong decision.

As for linting, go vet and [staticcheck](staticcheck.io) are the recommended tools, according to the now deprecated golint repository.

golint is deprecated, and it’s no longer required to comment every exported variable/function/struct, etc.

not found error (go tools not found issue explained below), can also check here

about Initialisms; Personally I still prefer simple initial conventions (lowerCamelCase, UpperCamelCase, UPPERCASE) Go followed before VSCODE/Microsoft suggested ID or Id (ex. https://github.com/golang/lint/issues/124). Following one pattern everywhere is the best. In Go, a name is exported if it begins with a capital letter. ex URL; if any unexported var/const start with "URL", what do you do?