Mmock VS mockery

Compare Mmock vs mockery and see what are their differences.

Mmock

Mmock is an HTTP mocking application for testing and fast prototyping (by jmartin82)
Our great sponsors
  • InfluxDB - Access the most powerful time series database as a service
  • SonarLint - Clean code begins in your IDE with SonarLint
  • SaaSHub - Software Alternatives and Reviews
Mmock mockery
0 17
641 4,691
- 2.7%
0.0 7.2
30 days ago 2 days ago
Go Go
MIT License 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.

Mmock

Posts with mentions or reviews of Mmock. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning Mmock yet.
Tracking mentions began in Dec 2020.

mockery

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-04-28.
  • I want to contribute to open source but don't know where to start
    9 projects | /r/golang | 28 Apr 2023
    There are some one liner changes you can implement in https://github.com/vektra/mockery
  • Is gomock still maintained and recommended?
    7 projects | /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 | /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 | /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 | /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 | /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 | /r/golang | 23 Oct 2021
    Gomock or mockery?

What are some alternatives?

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

gomock - GoMock is a mocking framework for the Go programming language.

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

minimock - Powerful mock generation tool for Go programming language

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

moq - Interface mocking tool for go generate

gotests - Automatically generate Go test boilerplate from your source code.

hoverfly - Lightweight service virtualization/ API simulation / API mocking tool for developers and testers

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

webmock - Webmock for Golang, to stub requests.