gomock VS mockery

Compare gomock vs mockery and see what are their differences.


GoMock is a mocking framework for the Go programming language. (by golang)
Our great sponsors
  • SonarQube - Static code analysis for 29 languages.
  • InfluxDB - Access the most powerful time series database as a service
  • SaaSHub - Software Alternatives and Reviews
gomock mockery
34 14
8,653 4,470
2.4% 4.6%
3.7 8.1
29 days ago 2 days ago
Go Go
Apache License 2.0 BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of gomock. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-06.
  • Is gomock still maintained and recommended?
    7 projects | reddit.com/r/golang | 6 Mar 2023
    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.
  • Want to know if this is a valid approach
    2 projects | reddit.com/r/golang | 2 Mar 2023
    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.
  • Go API Project Set-Up
    7 projects | dev.to | 23 Dec 2022
    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.
  • Google's internal Go style guide
    5 projects | reddit.com/r/golang | 18 Nov 2022
    Where we do use mocks, we primarily use GoMock.
  • How do you write/generate mocks for testing?
    5 projects | reddit.com/r/golang | 21 Sep 2022
    Currently migrating from moq to https://github.com/golang/mock
  • golang unit testing
    3 projects | dev.to | 3 Sep 2022
    I use gomock or mockery for mocking the interfaces and testify for evaluating tests
  • How we wrote Tarantool Kubernetes Operator
    13 projects | dev.to | 29 Jul 2022
    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.
  • how to mock DBs
    13 projects | reddit.com/r/golang | 30 May 2022
    In all other layers, my repositories are mocked using https://github.com/golang/mock
    13 projects | reddit.com/r/golang | 30 May 2022
  • How do you decide you are gonna use interface?
    2 projects | reddit.com/r/golang | 2 May 2022
    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


Posts with mentions or reviews of mockery. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-06.
  • Is gomock still maintained and recommended?
    7 projects | reddit.com/r/golang | 6 Mar 2023
    When there's just one heavyweight dependency you're interacting with, perhaps a one-off stub/fake is simpler, but I would posit that auto-generated mocks via things like mockery + go:generate leave less test code to maintain vs. perhaps many stubs across the project.
  • How do you write/generate mocks for testing?
    5 projects | reddit.com/r/golang | 21 Sep 2022
    My bread and butter is mockery (https://github.com/vektra/mockery). It has a few shortcomings (a config would be really nice in my project) which should be fixed in v3 (https://github.com/vektra/mockery#v3).
  • Layered Architectures in Go
    2 projects | dev.to | 3 Sep 2022
    One of the huge benefits to this pattern is testability. Since each layer is injected into each parent layer, we can generate mocks for each layer and inject those instead. For this code we could easily achieve 100% code coverage when unit testing each layer, since we have full control of the child layers. A great tool to use for generating mocks from interfaces is vektra/mokery. One command will create mocks for each of your interfaces that we can inject during test.
  • golang unit testing
    3 projects | dev.to | 3 Sep 2022
    I use gomock or mockery for mocking the interfaces and testify for evaluating tests
  • Show HN: Simple Go mocks without interface{}s
    2 projects | news.ycombinator.com | 27 May 2022
    Since mockery uses a lot of interface{} magic, adding arguments or return values to interfaces and regenerating the mocks does not get the compiler to complain about existing, now invalid, usages of the mocks. This means that I have to track them down manually. Or, if I'm brave enough, try my hand at a few crazy regexes that never get the job 100% done.

    go-mocky does not use interface{}s, and thus can't hide changes to function signatures from the compiler; whenever a mock has been updated and the function signature has changed, the compiler will complain for all existing tests. This means that I can now catch errors at compile/lint time instead of runtime.

    Another added benefit is that the go-mocky mocks are dead simple and very easy to write and maintain by hand, should the need ever arise.

    [1]: https://github.com/vektra/mockery

  • is there a way to write test in a sane way?
    3 projects | reddit.com/r/golang | 22 Mar 2022
    +1 on testify. Started out with that, and it, together with its mocks and the framework mockery are a brilliant combination, assuming you are into testing with mocks to some extent
  • How do you control behaviour in mocked interface ?
    5 projects | reddit.com/r/golang | 21 Jan 2022
    I use mockery to generate mocks based on my interfaces: https://github.com/vektra/mockery
  • How do you install commands using go.mod
    4 projects | reddit.com/r/golang | 2 Nov 2021
    There are some packages in my project that are not used in the source code, but they're used as commands (i.e. https://github.com/vektra/mockery https://github.com/rubenv/sql-migrate).
  • What mocking framework do you prefer?
    6 projects | reddit.com/r/golang | 23 Oct 2021
    Gomock or mockery?
  • mockcompose to generate mocking implementation for Go classes, interfaces and functions
    3 projects | reddit.com/r/golang | 6 Jul 2021
    As a Go newbie, the on-boarding process to Golang went relatively smoothly except a small glitch when it came to search for a mocking framework to test out a Go class implementation. I was a bit surprised to realize that I was not able to find a on-shelf tool to help me mock a class method. It might be an edge case scenario that I wanted to mock a class method, but I do believe that this is a valid use case, so I went ahead to spend a weekend building such a tool: mockcompose. It was originally aimed to just solve this one particular use case, therefore, it had to be used together with mockery (one of the great tools I found during my search in the period). I later refined the tool to cover mocking code generation for Go interfaces and functions, mockcompose can now be used in most of Go unit test scenarios. Please check it out and give it a try, I hope the tool is useful, feel free to drop your feedback and share with your opinion there.

What are some alternatives?

When comparing gomock and mockery you can also consider the following projects:

Testify - A toolkit with common assertions and mocks that plays nicely with the standard library

pgx - PostgreSQL driver and toolkit for Go

sqlx - general purpose extensions to golang's database/sql

monkey - Monkey patching in Go

counterfeiter - A tool for generating self-contained, type-safe test doubles in go

go-sqlmock - Sql mock driver for golang to test database interactions

minimock - Powerful mock generation tool for Go programming language

zerolog - Zero Allocation JSON Logger

gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽

moq - Interface mocking tool for go generate

realize - Realize is the #1 Golang Task Runner which enhance your workflow by automating the most common tasks and using the best performing Golang live reloading.