counterfeiter
A tool for generating self-contained, type-safe test doubles in go (by maxbrunsfeld)
mockhttp
Mock object for Go http.ResponseWriter (by tv42)
| counterfeiter | mockhttp | |
|---|---|---|
| 12 | - | |
| 920 | 23 | |
| - | - | |
| 7.5 | 0.0 | |
| 10 days ago | over 9 years ago | |
| Go | Go | |
| MIT License | MIT 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.
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.
counterfeiter
Posts with mentions or reviews of counterfeiter.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-07.
-
Mocking database calls without a library?
then just replace whole function, don't generate manually the mock '__') or it would get out of hand fast, you can just use codegen that static typed like https://github.com/maxbrunsfeld/counterfeiter
-
Is this a good way to make sure that a mocked function is called inside the Unit Test?
Yes, that's a good way to do that; there are a lot of packages that allow you to mock and spy the calls if you're looking for one that generates the code for you I can recommend counterfeiter, I also have a short blog that covers it.
-
Libraries you use most of your projects?
I prefer https://github.com/maxbrunsfeld/counterfeiter
-
How do you write/generate mocks for testing?
counterfeiter is another tool, it creates mocks, stubs and spies; here is a short blog I wrote covering it.
- Mocking Interfaces in Go with GoMock
- What's the best approach for mocking a function /method?
-
Best/Easiest Rest Framework
for dependency injection I suggest you use https://github.com/maxbrunsfeld/counterfeiter, but if you using really fast database (that can spawn fast using docker and has fast trx/sec) you can use it directly without dependency injection with https://github.com/ory/dockertest
-
Migrating from NodeJS/Typescript into Golang. Any advise for big web application?
Agree with u/mmknightx there is a tool that assist in creating fake or mock classes for your interfaces https://github.com/maxbrunsfeld/counterfeiter
-
How do you control behaviour in mocked interface ?
Another alternative to use would be counterfeiter, it generates a type from your interface that could be used as a mock, stub or spy. I wrote a short post covering that tool if you're interested.
- Slack notification Github action
mockhttp
Posts with mentions or reviews of mockhttp.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning mockhttp yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
When comparing counterfeiter and mockhttp you can also consider the following projects:
gomock - GoMock is a mocking framework for the Go programming language.
go-txdb - Immutable transaction isolated sql driver for golang
mockery - A mock code autogenerator for Go
gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽
Mmock - Mmock is an HTTP mocking application for testing and fast prototyping
prettybenchcmp - cmd tool for automatic storage and comparison of benchmarks results
minimock - Powerful mock generation tool for Go programming language
go-localstack - Go Wrapper for using localstack
govcr - HTTP mock for Golang: record and replay HTTP/HTTPS interactions for offline testing