counterfeiter

AFAICT that uses go/types, loaded uniquely per execution via packages.Load¹, which is by far the primary reason why e.g. go.uber.org/mock (previously github.com/golang/mock) can become extremely slow. mockery v3 does not do this. it type-checks just once for ALL mocks, regardless of the number, so it essentially does not grow slower as you create more mocks (since type checking is usually FAR slower than producing the mock). 1: https://github.com/maxbrunsfeld/counterfeiter/blob/000b82ca1...

Try https://github.com/maxbrunsfeld/counterfeiter

We make use of https://github.com/onsi/ginkgo and Gomega https://github.com/onsi/gomega for BDD testing with more expressive matchers. You might be familiar with some of these concepts from Cucumber/Jasmine/Mocha. They get significant use in Cloud Foundry and in the Kubernetes e2e tests. I appreciate a lot of people like the simplicity of the standard test library and if you're starting with Go development, it's not a bad idea to get used to that before exploring external dependencies. Caveat: While not necessarily a "maintainer", I have been doing a bunch of maintenance on these projects the past few weeks. Edit: Also we use counterfeiter https://github.com/maxbrunsfeld/counterfeiter for fakes.

If you're comfortable with this style of testing, you can do it in Go using interfaces and code generation. Counterfeiter hooks into `go generate`: https://github.com/maxbrunsfeld/counterfeiter Here's an example project: https://github.com/andreasf/cf-mysql-plugin

Counterfeiter is a pretty serviceable mock generator: https://github.com/maxbrunsfeld/counterfeiter