gomock VS zap

Compare gomock vs zap and see what are their differences.

gomock

GoMock is a mocking framework for the Go programming language. (by golang)

zap

Blazing fast, structured, leveled logging in Go. (by uber-go)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
gomock zap
40 51
9,010 20,762
- 1.6%
2.5 8.1
9 months ago 2 days ago
Go Go
Apache License 2.0 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.

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

zap

Posts with mentions or reviews of zap. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-27.
  • Building RESTful API with Hexagonal Architecture in Go
    21 projects | dev.to | 27 Sep 2023
    The project currently uses slog package from standard library for logging. But switching to a more advanced logger like zap could offer more flexibility and features.
  • Structured Logging with Slog
    11 projects | news.ycombinator.com | 22 Aug 2023
    It's nice to have this in the standard library, but it doesn't solve any existing pain points around structured log metadata and contexts. We use zap [0] and store a zap logger on the request context which allows different parts of the request pipeline to log with things like tenantid, traceId, and correlationId automatically appended. But getting a logger off the context is annoying, leads to inconsistent logging practices, and creates a logger dependency throughout most of our Go code.

    [0] https://github.com/uber-go/zap

    11 projects | news.ycombinator.com | 22 Aug 2023
    Oof. We just converted all of our logging to zap[0] to get structured JSON logging for downstream parsing. Wonder how the perf stacks up.

    [0]: https://github.com/uber-go/zap

  • Kubebuilder Tips and Tricks
    2 projects | dev.to | 22 Aug 2023
    Kubebuilder, like much of the k8s ecosystem, utilizes zap for logging. Out of the box, the Kubebuilder zap configuration outputs a timestamp for each log, which gets formatted using scientific notation. This makes it difficult for me to read the time of an event just by glancing at it. Personally, I prefer ISO 8601, so let's change it!
  • Go 1.21 Released
    7 projects | news.ycombinator.com | 8 Aug 2023
    What else would you expect from a structured logging package?

    To me it absolutely makes sense as the default and standard for 99% of applications, and the API isn't much unlike something like Zap[0] (a popular Go structured logger).

    The attributes aren't an "arbitrary" concept, they're a completely normal concept for structured loggers. Groups are maybe less standard, but reasonable nevertheless.

    I'm not sure if you're aware that this is specifically a structured logging package. There already is a "simple" logging package[1] in the sodlib, and has been for ages, and isn't particularly fast either to my knowledge. If you want really fast you take a library (which would also make sure to optimize allocations heavily).

    [0]: https://pkg.go.dev/go.uber.org/zap

    [1]: https://pkg.go.dev/log

  • Why elixir over Golang
    10 projects | /r/elixir | 29 May 2023
    And finally for structured logging: https://github.com/uber-go/zap
  • Beginner-friendly API made with Go following hexagonal architecture.
    5 projects | /r/golang | 21 May 2023
    For logging: I recommend using Uber Zap https://github.com/uber-go/zap It will log stack backtraces and makes it super easy to debug errors when deployed. I typically log in the business logic and not below. And log at the entry for failures to start the system. Maybe not necessary for this example, but it’s an essential piece of any API backend.
  • slogx - slog package extensions and middlewares
    3 projects | /r/golang | 1 May 2023
  • Why it is so weirdo??
    2 projects | /r/ProgrammerHumor | 22 Mar 2023
  • What is the common log library which is industry standard that is used in server applications?
    5 projects | /r/golang | 21 Mar 2023

What are some alternatives?

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

logrus - Structured, pluggable logging for Go.

zerolog - Zero Allocation JSON Logger

mockery - A mock code autogenerator for Go

slog

glog - Leveled execution logs 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