bimg
go-sqlmock
bimg | go-sqlmock | |
---|---|---|
5 | 19 | |
2,549 | 5,837 | |
- | 0.9% | |
3.9 | 5.4 | |
14 days ago | about 1 month 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.
bimg
-
Go Image Converting
h2non/bimg can handle both if the underlying libvips is compiled with support for both formats.
-
What is the coolest Go open source projects you have seen?
bimg
-
WASM instead of C Dependencies?
I have web applications written in Rust and Go that need some basic image processing (reading JPEGs, PNGs, writing JPEGs, WebPs, AVIFs and resizing). This is something I always struggle with, because most libraries for image processing are written in C (libpng, libwebp, mozjpeg; or higher-level ones like vips). While there are usually dependencies in each language build on top of those C dependencies, like bimg for Go, I don’t like having C dependencies in a Rust, Go or even Node.js projects.
- Image manipulation with Go
-
Image Compression with Golang
For image processing, I will use the bimg library because in my opinion it has a very intuitive API and is easy to use, in addition to being very fast.
go-sqlmock
- 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
-
[HELP] how to test this piece of code?
There is a good lib for db tests https://github.com/DATA-DOG/go-sqlmock
What are some alternatives?
govips - A lightning fast image processing and resizing library for Go
gomock - GoMock is a mocking framework for the Go programming language.
imaginary - Fast, simple, scalable, Docker-ready HTTP microservice for high-level image processing
go-txdb - Immutable transaction isolated sql driver for golang
imaging - Imaging is a simple image processing package for Go
mockery - A mock code autogenerator for Go
bild - Image processing algorithms in pure Go
gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽
goimagehash - Go Perceptual image hashing package
minimock - Powerful mock generation tool for Go programming language
fastimage - Finds the type and/or size of a remote image given its uri, by fetching as little as needed.
gotests - Automatically generate Go test boilerplate from your source code.