go-sqlmock VS mockery

Compare go-sqlmock vs mockery and see what are their differences.

go-sqlmock

Sql mock driver for golang to test database interactions (by DATA-DOG)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
go-sqlmock mockery
19 19
5,786 5,544
1.8% 2.7%
4.7 8.8
2 months ago 15 days ago
Go Go
GNU General Public License v3.0 or later BSD 3-clause "New" or "Revised" 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.

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
    5 projects | dev.to | 24 Oct 2022
    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?
    3 projects | /r/golang | 22 Oct 2022
    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
    3 projects | /r/golang | 22 Oct 2022
    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?
    84 projects | /r/golang | 15 Sep 2022
  • How to mock database calls
    4 projects | /r/golang | 27 Aug 2022
  • Can you set expectations for SQL transaction using Testify?
    2 projects | /r/golang | 17 Jul 2022
    I use Sqlmock for that purpose
  • Mocking database queries - ask for opinion
    6 projects | /r/golang | 9 Jul 2022
    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
    6 projects | /r/golang | 9 Jul 2022
  • I share my authentication server.
    18 projects | /r/golang | 20 Dec 2021
    Continuous Integration - Testify, sqlmock, Mockery, Github Actions
  • [HELP] Testing SQL queries and functions that use SQL queries in Golang.
    3 projects | /r/golang | 1 Dec 2021
    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.

mockery

Posts with mentions or reviews of mockery. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-26.
  • go-ecommerce-microservices: A practical e-commerce microservices, built with cqrs, event sourcing, vertical slice architecture, event-driven architecture.
    8 projects | /r/golang | 26 Aug 2023
    Some of the features: - ✅ Using Vertical Slice Architecture as a high level architecture - ✅ Using Event Driven Architecture on top of RabbitMQ Message Broker with a custom [Event Bus](pkg/messaging/bus/) - ✅ Using Event Sourcing in Audit Based services like [Orders Service](services/orders/) - ✅ Using CQRS Pattern and Mediator Patternon top of Go-MediatR library - ✅ Using Dependency Injection and Inversion of Controlon top of uber-go/fx library - ✅ Using RESTFul api with Echo framework and using swagger with swaggo/swag library - ✅ Using Postgres and EventStoreDB to write databases with fully supports transactions(ACID) - ✅ Using MongoDB and Elastic Search for read databases (NOSQL) - ✅ Using OpenTelemetry for collection Distributed Tracing with using Jaeger and Zipkin - ✅ Using OpenTelemetry for collection Metrics with using Prometheus and Grafana - ✅ Using Unit Test for testing small units with mocking dependent classes and using Mockery for mocking dependencies - ✅ Using End2End Test and Integration Test for testing features with all of their real dependeinces using docker containers (cleanup tests) and testcontainers-go library
  • I want to contribute to open source but don't know where to start
    9 projects | /r/golang | 28 Apr 2023
    There are some one liner changes you can implement in https://github.com/vektra/mockery
  • Is gomock still maintained and recommended?
    7 projects | /r/golang | 6 Mar 2023
    When there's just one heavyweight dependency you're interacting with, perhaps a one-off stub/fake is simpler, but I would posit that auto-generated mocks via things like mockery + go:generate leave less test code to maintain vs. perhaps many stubs across the project.
  • How do you write/generate mocks for testing?
    5 projects | /r/golang | 21 Sep 2022
    My bread and butter is mockery (https://github.com/vektra/mockery). It has a few shortcomings (a config would be really nice in my project) which should be fixed in v3 (https://github.com/vektra/mockery#v3).
  • Layered Architectures in Go
    2 projects | dev.to | 3 Sep 2022
    One of the huge benefits to this pattern is testability. Since each layer is injected into each parent layer, we can generate mocks for each layer and inject those instead. For this code we could easily achieve 100% code coverage when unit testing each layer, since we have full control of the child layers. A great tool to use for generating mocks from interfaces is vektra/mokery. One command will create mocks for each of your interfaces that we can inject during test.
  • golang unit testing
    3 projects | dev.to | 3 Sep 2022
    I use gomock or mockery for mocking the interfaces and testify for evaluating tests
  • Show HN: Simple Go mocks without interface{}s
    2 projects | news.ycombinator.com | 27 May 2022
    Since mockery uses a lot of interface{} magic, adding arguments or return values to interfaces and regenerating the mocks does not get the compiler to complain about existing, now invalid, usages of the mocks. This means that I have to track them down manually. Or, if I'm brave enough, try my hand at a few crazy regexes that never get the job 100% done.

    go-mocky does not use interface{}s, and thus can't hide changes to function signatures from the compiler; whenever a mock has been updated and the function signature has changed, the compiler will complain for all existing tests. This means that I can now catch errors at compile/lint time instead of runtime.

    Another added benefit is that the go-mocky mocks are dead simple and very easy to write and maintain by hand, should the need ever arise.

    [1]: https://github.com/vektra/mockery

  • is there a way to write test in a sane way?
    3 projects | /r/golang | 22 Mar 2022
    +1 on testify. Started out with that, and it, together with its mocks and the framework mockery are a brilliant combination, assuming you are into testing with mocks to some extent
  • How do you control behaviour in mocked interface ?
    5 projects | /r/golang | 21 Jan 2022
    I use mockery to generate mocks based on my interfaces: https://github.com/vektra/mockery
  • How do you install commands using go.mod
    4 projects | /r/golang | 2 Nov 2021
    There are some packages in my project that are not used in the source code, but they're used as commands (i.e. https://github.com/vektra/mockery https://github.com/rubenv/sql-migrate).

What are some alternatives?

When comparing go-sqlmock and mockery you can also consider the following projects:

gomock - GoMock is a mocking framework for the Go programming language.

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

go-txdb - Immutable transaction isolated sql driver for golang

minimock - Powerful mock generation tool for Go programming language

gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽

gotests - Automatically generate Go test boilerplate from your source code.

hoverfly - Lightweight service virtualization/ API simulation / API mocking tool for developers and testers

tidb-lite - Using tidb-lite to create a TiDB server with mocktikv mode in your application or unit test.

moq - Interface mocking tool for go generate

realize - Realize is the #1 Golang Task Runner which enhance your workflow by automating the most common tasks and using the best performing Golang live reloading.