mockcompose
go-sqlmock
| mockcompose | go-sqlmock | |
|---|---|---|
| 3 | 20 | |
| 15 | 6,048 | |
| - | 1.2% | |
| 3.3 | 4.9 | |
| about 1 year ago | 2 days ago | |
| Go | Go | |
| MIT License | GNU General Public License v3.0 or later |
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.
mockcompose
-
mockcompose to generate mocking implementation for Go classes, interfaces and functions
Part of reason that I went ahead to build mockcompose was for to improve test coverage of an existing project without major refactoring. Another reason is for completeness of a mocking tool to cover all possible aspects in unit-test scenarios that Go technically allows. It was meant to use it with Go best practices in mind.
- Mockcompose to mock Go classes,interfaces and functions
go-sqlmock
- 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
What are some alternatives?
mockery - A mock code autogenerator for Go
gomock - GoMock is a mocking framework for the Go programming language.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
go-txdb - Immutable transaction isolated sql driver for golang
hoverfly - Lightweight service virtualization/ API simulation / API mocking tool for developers and testers
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.
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