gomock VS zerolog

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

I use zerolog myself and have seen it being used in production several times. Also they have a list of who uses zerolog

This would be so awesome if it was extending an awesome logger like https://github.com/rs/zerolog. Personally I love zerolog because of how it handles different data types including structs!

logrus README recommended using other libraries such as Zerolog, Zap, and Apex.

I'd recommend checking out https://github.com/spf13/viper for configurations and https://github.com/rs/zerolog for enhanced logging.

zerolog

Many fantastic alternatives have sprung up. Logrus would look like those, had it been re-designed with what we know about structured logging in Go today. Check out, for example, Zerolog, Zap, and Apex.

My only issue with zerolog is that there has been no new releases in 5 years. Which means there are fairly serious/embarassing issues (e.g. https://github.com/rs/zerolog/issues/319) which have been fixed in master but still affect the "stable" v1.0.0 release... I have no idea why they don't cut a new release.

This may be helpful to you. https://github.com/learning-cloud-native-go/myapp/blob/master/util/logger/logger.go . However it's just a wrapper for https://github.com/rs/zerolog/blob/master/log/log.go .