counterfeiter VS go-sqlmock

for dependency injection I suggest you use https://github.com/maxbrunsfeld/counterfeiter, but if you using really fast database (that can spawn fast using docker and has fast trx/sec) you can use it directly without dependency injection with https://github.com/ory/dockertest

Agree with u/mmknightx there is a tool that assist in creating fake or mock classes for your interfaces https://github.com/maxbrunsfeld/counterfeiter

Another alternative to use would be counterfeiter, it generates a type from your interface that could be used as a mock, stub or spy. I wrote a short post covering that tool if you're interested.

Correct link is https://github.com/maxbrunsfeld/counterfeiter for those interested

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

Continuous Integration - Testify, sqlmock, Mockery, Github Actions

For testing DB queries I use https://github.com/DATA-DOG/go-sqlmock for unit tests. I then have a separate integration test suite that runs against all our services using Docker.

However your point is valid. Check matryer/is for unit test writing. DATA-DOG/go-sqlmock to test database interactions.

We have different ways to write our tests depending on what datastore we are using, for example if we are testing database calls that happen to be using database/sql then importing a package like github.com/DATA-DOG/go-sqlmock could work.

Another common method is to mock SQL services in the test. At present, the more popular solution is to use go-sqlmock.

I've been using https://github.com/DATA-DOG/go-sqlmock. It's pretty well documented, should be enough to get going.

I've never bothered with any ORM, but for mocking the underlying sql.DB I've been using https://github.com/DATA-DOG/go-sqlmock which is very simple and straightforward to use.