Pgxmock Alternatives

Similar projects and alternatives to pgxmock based on common topics and language

go-sqlmock

19 5,817 5.4 Go pgxmock VS go-sqlmock

Sql mock driver for golang to test database interactions
pgxatomic

2 8 10.0 Go pgxmock VS pgxatomic

Clean implementation of transaction manager using pgx
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
goose

28 5,637 8.9 Go pgxmock VS goose

A database migration tool. Supports SQL migrations and Go functions.
pig

0 16 4.3 Go pgxmock VS pig

Simple pgx wrapper to execute and scan query results
scany

5 1,183 4.9 Go pgxmock VS scany

Library for scanning data from a database into Go structs and more
usql

21 8,605 9.0 Go pgxmock VS usql

Universal command-line interface for SQL databases
FerretDB

43 8,509 9.8 Go pgxmock VS FerretDB

A truly Open Source MongoDB alternative
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better pgxmock alternative or higher similarity.

Suggest an alternative to pgxmock

pgxmock reviews and mentions

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?
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.
Can you set expectations for SQL transaction using Testify?
2 projects | /r/golang | 17 Jul 2022

For postgres only but pgxmock is similarly excellent