mockery
Mmock
Our great sponsors
| mockery | Mmock | |
|---|---|---|
| 7 | 0 | |
| 3,756 | 612 | |
| 3.3% | - | |
| 8.3 | 0.0 | |
| 25 days ago | about 2 months ago | |
| Go | Go | |
| BSD 3-clause "New" or "Revised" License | MIT License |
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.
mockery
-
On interfaces and composition
Mockery is a great tool to generate mocks based on interfaces, that way our unit tests can look like this (pseudocode):
-
Show HN: Simple Go mocks without interface{}s
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.
-
is there a way to write test in a sane way?
+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 ?
I use mockery to generate mocks based on my interfaces: https://github.com/vektra/mockery
-
How do you install commands using go.mod
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?
Gomock or mockery?
-
mockcompose to generate mocking implementation for Go classes, interfaces and functions
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.
Mmock
We haven't tracked posts mentioning Mmock yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
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
hoverfly - Lightweight service virtualization/API simulation tool for developers and testers
gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽
monkey - Monkey patching in Go
mockhttp - Mock object for Go http.ResponseWriter