versioninfo
dockertest
versioninfo | dockertest | |
---|---|---|
6 | 48 | |
237 | 3,983 | |
- | 1.4% | |
3.7 | 3.0 | |
10 months ago | 2 days ago | |
Go | Go | |
MIT License | Apache License 2.0 |
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.
versioninfo
-
Libraries you use most of your projects?
Oh, also https://github.com/carlmjohnson/versioninfo . Always need that.
-
FreePad | A free self-hosted pad written in go
Don’t. It’s obsolete. Just use debug.ReadBuildInfo()
-
Makefile and Dockerfile best practices
That’s obsolete. See https://github.com/carlmjohnson/versioninfo. Even if it weren’t, Make is an inappropriate tool. Because it is based on file modtimes, it can’t react to git hash changes. You just have rerun the steps every time, at which point Bash is a less awful language.
-
How to embed version when `go install`-ing (since you cannot use go:generate or ldflags -X)
Go 1.18 updates the debug info to also include the git status of the build. See https://github.com/carlmjohnson/versioninfo
-
Go 1.18 - debug/info - why not include the current git tag?
I use this trick in my versioninfo package. Obviously, it can't give you other tags, but most of the time the tag you want to know about is v1.2.3 anyway, and since tags are mutable but the Go sum DB is immutable, this is safer than just saying what tag was on disk at build time.
-
Getting excited for Go 1.18's lesser known features
I subscribed to GH activity for the correspondence friendliness-enhancing library by the author:
https://github.com/carlmjohnson/versioninfo/
The primary motivation curiousity to learn if this becomes "the [best/default] way" folks reach for when leveraging BuildInfo to deliver explicit binary versioning.
dockertest
-
Testcontainers
I am using https://github.com/ory/dockertest for tests, specifically for databases. Is there any advantage to use Testcontainers?
-
Level UP your RDBMS Productivity in GO
Now, let's run the tests. For this purpose, we are going to use dockertest, but test containers is also a good solution.
-
Golang testing using docker services via dockertest
During my path learning go so far I have come across some amazing libraries and utilites, one of my favourite for integration testing is dockertest.
-
How to start a Go project in 2023
Things I can't live without in a new Go project in no particular order:
- https://github.com/golangci/golangci-lint - meta-linter
- https://goreleaser.com - automate release workflows
- https://magefile.org - build tool that can version your tools
- https://github.com/ory/dockertest/v3 - run containers for e2e testing
- https://github.com/ecordell/optgen - generate functional options
- https://golang.org/x/tools/cmd/stringer - generate String()
- https://mvdan.cc/gofumpt - stricter gofmt
- https://github.com/stretchr/testify - test assertion library
- https://github.com/rs/zerolog - logging
- https://github.com/spf13/cobra - CLI framework
FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb
We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/tree/main/tools/analyzers
-
Beginner-friendly API made with Go following hexagonal architecture.
I've used dockertest a bunch and it is really amazing.
-
How to unit test your database interactions with Docker
Reminds me of https://github.com/ory/dockertest
-
When to mock and what to mock in a Web API?
If your project is relatively simple and you can get away with recreating your scenarios against a real mock database and run other related services locally. It would be good to setup docker containers for your test scripts and write e2e tests. I believe e2e tests are harder but more useful in understanding/reasoning how users are impacted.
-
Don't Mock the Database
Just a heads up, the repository in your comment is invalid, the correct link is https://github.com/ory/dockertest
-
Mocking database calls without a library?
Don't mock. Use https://github.com/ory/dockertest to actually run tests against a dockerized DB.
-
Different SQL drivers for test and production
Use a library like ory/dockertest to spin up a test database for integration tests. It's easy to use, and tests are still fast. It'll take a minute to download the mysql docker image the first time. But, once it's been downloaded, starting the db, running migrations, and running the tests is still pretty quick.
What are some alternatives?
assert - A simple assertion library using Go generics
testcontainers-go - Testcontainers for Go is a Go package that makes it simple to create and clean up container-based dependencies for automated integration/smoke tests. The clean, easy-to-use API enables developers to programmatically define containers that should be run as part of a test and clean up those resources when the test is done.
FreePad - FreePad is a simple Go project to help you juggle temporary notes that you might wanna pass from one device to another, or from a person to another with memorable and easy to communicate online "Pads".
fake-gcs-server - Google Cloud Storage emulator & testing library.
flagx - Extensions to the Go flag package
mockaroo - Mock-A-🦘 (mock-aa-roo) a comprehensive HTTP/HTTPS interface mocking tool for all your development and testing needs!
venom - 🐍 Manage and run your integration tests with efficiency - Venom run executors (script, HTTP Request, web, imap, etc... ) and assertions
steampipe - Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
go-sqlmock - Sql mock driver for golang to test database interactions
go-mockgen-tool - Go/Golang mock generation for interfaces via code generation
sqlc - Generate type-safe code from SQL
gnomock - Test your code without writing mocks with ephemeral Docker containers 📦 Setup popular services with just a couple lines of code ⏱️ No bash, no yaml, only code 💻