Boosting Test Coverage for Microservices
summary
Shows how to get real coverage from running microservices by instrumenting binaries with the Go 1.20 cover flag, building images that write coverage files, and running tests via Docker Compose inside GitHub Actions so coverage can be uploaded to codecov.io. Implementation includes a custom GitHub Action, mapping a coverage folder out of the container, and fixing graceful shutdown so files are flushed. Result: one service gains almost 5 percentage points of reported coverage and hidden untested files are discovered.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 6:51Automated testing essentials
- 10:08Unit vs application tests
- 19:51Visualizing coverage data
- 24:11Coverage percentage limits
- 27:50CI pipeline monitoring
- 28:35Coverage with Go 1.20
- 33:11Refactoring CI pipeline
- 37:10Results and insights
- 40:46Key takeaways
related talks
40mBoosting test coverage for microservices
07mGenerating Coverage with System Test
57mComprehensive testing strategies for modern microservice architectures
31mMeasure End to End Tests Coverage
43mTest coverage in Go, the whole package
42mUse Docker to test microservices
47mDev/Testing challenges with microservices and CD
28mContinuous Integration Testing: Fully Test your Microservices Application, Early and Often