goleak
testcontainers-go
goleak | testcontainers-go | |
---|---|---|
6 | 18 | |
4,302 | 3,169 | |
1.8% | 6.4% | |
5.8 | 9.7 | |
14 days ago | 3 days ago | |
Go | Go | |
MIT License | 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.
goleak
-
The Case of a Leaky Goroutine
Didn't Uber have some leaky goroutine detector? I vaguely remember seeing something like that, 5 years ago...
Ah yeah it's here.
https://github.com/uber-go/goleak
- How to start a Go project in 2023
-
A lib for goroutine leak detection
The reason why I created this project is because they don't want to make the goleak more flexible: https://github.com/uber-go/goleak/pull/52
-
Finding Goroutine Leaks in Tests
In the past, I had used https://github.com/uber-go/goleak . I hadn't looked into how it does it, but I think it's a different approach than what you wrote about. Do you have any idea what are the differences?
-
Question about integration tests and stopping goroutines
In the past, I have used this: https://github.com/uber-go/goleak . But it's not ideal, as AFAIK there isn't really a deterministic way to wait until a goroutine has actually stopped. That is, if you want to test that a goroutine has stopped, you'll end up with non-determinism, thus flaky tests.
-
Finding blocked goroutines
https://github.com/uber-go/goleak - checks for tests
testcontainers-go
-
Using test helpers in Go
Let's first look at the original version of the test, in this case, an end-to-end, using testcontainers.
-
Run and test DynamoDB applications locally using Docker and Testcontainers
It supports multiple languages (including Go!) and databases (also messaging infrastructure etc.) - All you need is Docker. Testcontainers for Go makes it simple to programmatically create and clean up container-based dependencies for automated integration/smoke tests. You can define test dependencies as code, run tests and delete the containers once done.
-
๐ Effortless Integration Tests with Testcontainers in Golang ๐งช
Testcontainers Go Documentation
-
go-ecommerce-microservices: A practical e-commerce microservices, built with cqrs, event sourcing, vertical slice architecture, event-driven architecture.
Some of the features: - โ Using Vertical Slice Architecture as a high level architecture - โ Using Event Driven Architecture on top of RabbitMQ Message Broker with a custom [Event Bus](pkg/messaging/bus/) - โ Using Event Sourcing in Audit Based services like [Orders Service](services/orders/) - โ Using CQRS Pattern and Mediator Patternon top of Go-MediatR library - โ Using Dependency Injection and Inversion of Controlon top of uber-go/fx library - โ Using RESTFul api with Echo framework and using swagger with swaggo/swag library - โ Using Postgres and EventStoreDB to write databases with fully supports transactions(ACID) - โ Using MongoDB and Elastic Search for read databases (NOSQL) - โ Using OpenTelemetry for collection Distributed Tracing with using Jaeger and Zipkin - โ Using OpenTelemetry for collection Metrics with using Prometheus and Grafana - โ Using Unit Test for testing small units with mocking dependent classes and using Mockery for mocking dependencies - โ Using End2End Test and Integration Test for testing features with all of their real dependeinces using docker containers (cleanup tests) and testcontainers-go library
- How to start a Go project in 2023
-
Questions about Interfacing for Unit-Tests
For example, you could take a look at this open-source project that helps you spawn docker containers as part of your test setup enabling you to execute queries to a local database.
-
How to Work with SQL Databases in Go
Using something like TestContainers to spin up a DB for testing has been my best experience. Any mocks leave too much room for error imo
-
Different SQL drivers for test and production
I highly recommend testcontainers for this.
-
Go API Project Set-Up
The next block in .gitlab-ci.yml is the services block. Since our tests use testcontainers package and we're pushing a docker container onto Dockerhub, we will need to specify a services block next. Services will enable our pipeline to leverage Docker-in-Docker DinD.
- Do you test your API, repositories, & services together (e.g., e2e) or separately?
What are some alternatives?
go - The Go programming language
dockertest - Write better integration tests! Dockertest helps you boot up ephermal docker images for your Go tests with minimal work.
gotrace - A lib for monitoring runtime goroutine stack
otj-pg-embedded - Java embedded PostgreSQL component for testing
gow - Missing watch mode for Go commands. Watch Go files and execute a command like "go run" or "go test"
venom - ๐ Manage and run your integration tests with efficiency - Venom run executors (script, HTTP Request, web, imap, etc... ) and assertions
thefuck - Magnificent app which corrects your previous console command.
testcontainers-dotnet - A library to support tests with throwaway instances of Docker containers for all compatible .NET Standard versions.
goda - Go Dependency Analysis toolkit
localstripe - A fake but stateful Stripe server that you can run locally, for testing purposes.
reflex - Run a command when files change
integresql - IntegreSQL manages isolated PostgreSQL databases for your integration tests.