go-sqlmock VS go-txdb

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

go-sqlmock

Sql mock driver for golang to test database interactions (by DATA-DOG)

go-txdb

Immutable transaction isolated sql driver for golang (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 go-txdb
19 2
5,739 606
1.0% 0.7%
4.7 6.9
about 2 months ago about 2 months ago
Go Go
GNU General Public License v3.0 or later 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.

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.

go-txdb

Posts with mentions or reviews of go-txdb. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-29.
  • Integration Tests with Postgres
    2 projects | /r/golang | 29 Mar 2023
    3 years ago I created a internal library where I worked to setup the testing with the db's. One param was the schema directory and the other one was the path of the data insertion file. It worked really well but was a little slow. It was a little bit weird to configure the container to run the tests. As I would have to give access to go container that ran the unit tests access to docker. But back then I was running boot2docker and made things very cumbersome. I think with a local docker things would be way simpler. I ended up using and normal DB from the CI/CD and https://github.com/DATA-DOG/go-txdb If I had to do it again I might do an hybrid in-between the two solutions
  • Unit Testing a Grom Application With a Real DB Server
    3 projects | /r/golang | 27 Jul 2022
    The first one is TestMain, which could improve the lifecycle management of the container. The second one is DATA-DOG/go-txdb, this allows you to open a new db connection running in a transaction, so each test could have its own isolated DB connection.

What are some alternatives?

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

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

mockery - A mock code autogenerator for Go

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

minimock - Powerful mock generation tool for Go programming language

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

mockhttp - Mock object for Go http.ResponseWriter

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

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.

Mmock - Mmock is an HTTP mocking application for testing and fast prototyping

Fake - Fake data generator for Go (Golang)