pgxmock
pgx mock driver for golang to test database interactions (by pashagolub)
pgxatomic
Clean implementation of transaction manager using pgx (by ysomad)
pgxmock | pgxatomic | |
---|---|---|
2 | 2 | |
282 | 8 | |
- | - | |
8.1 | 10.0 | |
9 days ago | over 1 year 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.
pgxmock
Posts with mentions or reviews of pgxmock.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-22.
-
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.
-
Can you set expectations for SQL transaction using Testify?
For postgres only but pgxmock is similarly excellent
pgxatomic
Posts with mentions or reviews of pgxatomic.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Database transactions with future changes to generics in mind
You can try this one: https://github.com/ysomad/pgxatomic
-
Library for implementing clean transactions with pgx
Hello, my name is Alex and I've implemented a simple set of wrappers for pgx transactions so that they can be used in a clean architecture, so that transactions can be managed from the application layer without abstractions flowing. I hope someone will find it useful, any criticism, questions and of course pull requests are welcome!
What are some alternatives?
When comparing pgxmock and pgxatomic you can also consider the following projects:
go-sqlmock - Sql mock driver for golang to test database interactions
goqux - Library for simple CRUD, scanning & pagination using query builder in golang
goose - A database migration tool. Supports SQL migrations and Go functions.
scany - Library for scanning data from a database into Go structs and more
Go-Clean-Architecture-REST-API - Golang Clean Architecture REST API example
Hexagonal-Architecture - a distributed messaging and payment backend built around the hexagonal architecture
Go-gRPC-RabbitMQ-microservice - Go gRPC RabbitMQ email microservice