go-sqlmock
Sql mock driver for golang to test database interactions (by DATA-DOG)
Mmock
Mmock is an HTTP mocking application for testing and fast prototyping (by jmartin82)
| go-sqlmock | Mmock | |
|---|---|---|
| 20 | - | |
| 6,097 | 675 | |
| 1.2% | - | |
| 4.9 | 7.4 | |
| about 1 month ago | 20 days ago | |
| Go | Go | |
| GNU General Public License v3.0 or later | 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.
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.
- Princípios SOLID em GoLang - Dependency Inversion Principle (DIP)
- How do you unit-test code that reaches out to the db, without introducing interfaces everywhere?
-
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?
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
- SQL mock driver for Golang to test database interactions
- Can't get a specifc SQL query with pgx to work
Mmock
Posts with mentions or reviews of Mmock.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning Mmock yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
When comparing go-sqlmock and Mmock 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
counterfeiter - A tool for generating self-contained, type-safe test doubles in go
mockery - A mock code autogenerator for Go
gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽
gotests - Automatically generate Go test boilerplate from your source code.
minimock - Powerful mock generation tool for Go programming language
mockhttp - Mock object for Go http.ResponseWriter
monkey - Monkey patching in Go