gomock VS counterfeiter

Looking at gomock's commit history, it seems like there hasn't been much activity on the project in a couple of years. I'm wondering if this is the case of software being mostly done and just in maintenance mode, or if gomock is falling behind. The reason I fear for the latter is there are still issues being opened up that don't seem to be engaged very much.

Yeah, that would work just fine. Nevertheless, as your business logic gets more complicated, you will want to test more scenarios and mocks will get complicated fast. In these cases tools like gomock really shine and make your life easier. I understand that this is a just-for-fun project, but it's never too early to experiment with a popular solution, especially if you plan on using Go professionally in the future.

Unit tests are leveraged to test individual units of code. As such it is not recommended for a developer to scaffold entire dependencies for the sake of testing a single object. Due to the way Go's specific implementations work, I've learned over time to declare interfaces for a lot of the structs that I use in Go. Interfaces not only define a contract for which struct-based implementations should adhere, but they also provide a mechanism for which struct methods can be mocked. While I've experimented with the mock package in testify, I've come to prefer the mock functionality which is provided by mockgen.

Where we do use mocks, we primarily use GoMock.

Currently migrating from moq to https://github.com/golang/mock

I use gomock or mockery for mocking the interfaces and testify for evaluating tests

As every software, the operator needs to be tested. In our case, we use two types of tests: Unit and E2E. For testing, usually mock code generation is used (for example, via golang/mock). We didn't like this option, so we decided to use Testify's mock module that allows to mock required function interfaces using the reflection API—the interfaces used to configure Tarantool.

In all other layers, my repositories are mocked using https://github.com/golang/mock

If you don't know how to mock databases, checkout some tutorials on it, it's a big topic, and I can't give you all the details on it. Checkout these repositories, they are used for mocking in golang https://github.com/golang/mock, https://github.com/stretchr/testify

then just replace whole function, don't generate manually the mock '__') or it would get out of hand fast, you can just use codegen that static typed like https://github.com/maxbrunsfeld/counterfeiter

https://github.com/maxbrunsfeld/counterfeiter - generate static typed test double (can be used to mock or stub calls)

I prefer https://github.com/maxbrunsfeld/counterfeiter

counterfeiter is another tool, it creates mocks, stubs and spies; here is a short blog I wrote covering it.

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