gotests VS gomock

Compare gotests vs gomock and see what are their differences.

gomock

GoMock is a mocking framework for the Go programming language. (by golang)
Our great sponsors
  • WorkOS - The modern API for authentication & user identity.
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • LearnThisRepo.com - Learn 300+ open source libraries for free using AI.
gotests gomock
10 40
4,805 9,010
- -
0.0 2.5
6 months ago 8 months ago
Go Go
Apache License 2.0 Apache License 2.0
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.

gotests

Posts with mentions or reviews of gotests. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-05.

gomock

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-06-28.
  • Google Stopped Maintaining GoMock
    2 projects | news.ycombinator.com | 28 Jun 2023
    The commit mentions this rather sad thread: https://github.com/golang/mock/pull/627#issuecomment-1605169...
    2 projects | news.ycombinator.com | 28 Jun 2023
  • Tools besides Go for a newbie
    36 projects | /r/golang | 26 Mar 2023
    IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
  • When to mock and what to mock in a Web API?
    3 projects | /r/golang | 23 Mar 2023
    Normally I like to generate everything with Mockgen and test it using table driven test.
  • Is gomock still maintained and recommended?
    7 projects | /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 | /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 | /r/golang | 18 Nov 2022
    Where we do use mocks, we primarily use GoMock.
  • How do you write/generate mocks for testing?
    5 projects | /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

What are some alternatives?

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

mockery - A mock code autogenerator for Go

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

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

monkey - Monkey patching 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

wire - Compile-time Dependency Injection for Go