|over 1 year ago||about 1 month ago|
|GNU General Public License v3.0 only||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.
We haven't tracked posts mentioning realize yet.
Tracking mentions began in Dec 2020.
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 | reddit.com/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 calls3 projects | reddit.com/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 | reddit.com/r/golang | 15 Sep 2022
How to mock database calls
4 projects | reddit.com/r/golang | 27 Aug 2022
Can you set expectations for SQL transaction using Testify?
2 projects | reddit.com/r/golang | 17 Jul 2022
I use Sqlmock for that purpose
Mocking database queries - ask for opinion
6 projects | reddit.com/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 net6 projects | reddit.com/r/golang | 9 Jul 2022
I share my authentication server.
18 projects | reddit.com/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 | reddit.com/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.
What are some alternatives?
gomock - GoMock is a mocking framework for the Go programming language.
go-txdb - Immutable transaction isolated sql driver for golang
chromedp - A faster, simpler way to drive browsers supporting the Chrome DevTools Protocol.
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.
go-fuzz - Randomized testing for Go
selenoid - Selenium Hub successor running browsers within containers. Scalable, immutable, self hosted Selenium-Grid on any platform with single binary.
mockery - A mock code autogenerator for Golang
cdp - Package cdp provides type-safe bindings for the Chrome DevTools Protocol (CDP), written in the Go programming language.
tidb-lite - Using tidb-lite to create a TiDB server with mocktikv mode in your application or unit test.