gomock
GoMock is a mocking framework for the Go programming language. (by golang)
DISCONTINUED
go-sqlmock
Sql mock driver for golang to test database interactions (by DATA-DOG)
Our great sponsors
gomock | go-sqlmock | |
---|---|---|
40 | 19 | |
9,010 | 5,786 | |
- | 1.8% | |
2.5 | 4.7 | |
9 months ago | 2 months ago | |
Go | Go | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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
The commit mentions this rather sad thread: https://github.com/golang/mock/pull/627#issuecomment-1605169...
-
Tools besides Go for a newbie
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?
Normally I like to generate everything with Mockgen and test it using table driven test.
-
Is gomock still maintained and recommended?
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
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
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
Where we do use mocks, we primarily use GoMock.
-
How do you write/generate mocks for testing?
Currently migrating from moq to https://github.com/golang/mock
-
golang unit testing
I use gomock or mockery for mocking the interfaces and testify for evaluating tests
go-sqlmock
Posts with mentions or reviews of go-sqlmock.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-24.
-
Creating an API using Go and sqlc
For that, I used the lib go-sqlmock. So, for example, the following snippet is part of the person/service_test.go file:
-
Using SQLC in project how do I mock database Calls with it for unit testing?
I’m writing a post about it! I will post soon, but you can use https://github.com/DATA-DOG/go-sqlmock to mock your database calls
It's not the right call IMO to skip mocking the database connection to achieve 100% test coverage. How your app will behave in failure scenarios that are impossible to imitate during integration tests is part of the software contract. If your choice is to panic, or return an error, document that by testing that behavior. If another dev, or future you inadvertently breaks the contract, the test suite will fail. That's what you want. For unit tests against your database you should be using either go-sqlmock if testing against database/sql or pgxmock if testing against pgx. That being said, the points raised elsewhere in this thread regarding unit tests potentially hiding edge cases in terms of how an actual database will interact with your application that are not reflective of your understanding when writing mocks are 100% valid. You should do both. Unit test your app and write integration tests as well. On my team, we run integration tests using docker-compose.
- What is the coolest Go open source projects you have seen?
- How to mock database calls
-
Can you set expectations for SQL transaction using Testify?
I use Sqlmock for that purpose
-
Mocking database queries - ask for opinion
I use https://github.com/DATA-DOG/go-sqlmock for unit testing my data layer code. Most of the times, these tests help me to find errors whenever I do a refactor on the data layer, so I consider it a good safety net
-
I share my authentication server.
Continuous Integration - Testify, sqlmock, Mockery, Github Actions
-
[HELP] Testing SQL queries and functions that use SQL queries in Golang.
For testing DB queries I use https://github.com/DATA-DOG/go-sqlmock for unit tests. I then have a separate integration test suite that runs against all our services using Docker.
What are some alternatives?
When comparing gomock and go-sqlmock 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
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
go-txdb - Immutable transaction isolated sql driver for golang