dockertest
pgxtutorial
dockertest | pgxtutorial | |
---|---|---|
48 | 3 | |
3,978 | 115 | |
1.3% | - | |
3.0 | 6.8 | |
10 days ago | 5 months ago | |
Go | Go | |
Apache License 2.0 | MIT License |
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.
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.
pgxtutorial
-
Back to basics: Writing an application using Go and PostgreSQL with pgx
# Clone my repository with any of the following commands: $ gh repo clone henvic/pgxtutorial $ git clone https://github.com/henvic/pgxtutorial.git $ git clone [email protected]:henvic/pgxtutorial.git # then: $ cd pgxtutorial # Create a database $ psql -c "CREATE DATABASE pgxtutorial;" # Set the environment variable PGDATABASE $ export PGDATABASE=pgxtutorial # Run migrations $ tern migrate -m ./migrations # Run all tests passing INTEGRATION_TESTDB explicitly $ INTEGRATION_TESTDB=true go test -v ./... # Execute application $ go run ./cmd/pgxtutorial 2021/11/22 07:21:21 HTTP server listening at localhost:8080 2021/11/22 07:21:21 gRPC server listening at 127.0.0.1:8082
-
Back to basics: Writing an application using Go and PostgreSQL
oh, I also have defined database.PGX (https://github.com/henvic/pgxtutorial/blob/main/internal/dat...), which is a little more scarier. I'll get back about that too, but this one is perhaps even more useless, and there might be a better way to solve the issue I want to try to avoid with it.
What are some alternatives?
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.
go-mockgen-tool - Go/Golang mock generation for interfaces via code generation
fake-gcs-server - Google Cloud Storage emulator & testing library.
pq - Pure Go Postgres driver for database/sql
mockaroo - Mock-A-🦘 (mock-aa-roo) a comprehensive HTTP/HTTPS interface mocking tool for all your development and testing needs!
litestream - Streaming replication for SQLite.
venom - 🐍 Manage and run your integration tests with efficiency - Venom run executors (script, HTTP Request, web, imap, etc... ) and assertions
whatgotdone - A tool for sharing weekly task updates with teammates.
steampipe - Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
impl - impl generates method stubs for implementing an interface.
go-sqlmock - Sql mock driver for golang to test database interactions
ApacheKafka - A curated re-sources list for awesome Apache Kafka