Comprehensive testing strategies for modern microservice architectures
summary
A Go microservice demo exposes /events and /events/{id} and shows exact tools and pipelines: unit tests and fuzz testing (Go fuzz target on talk title, run with -fuzz and -fuztime=5s), integration tests with net/http/httptest, containerized E2E using testcontainers against a Docker Hub image, and consumer-driven contract tests using the pack DSL published to packed flow; GitHub Actions run staged checks (fast local units, integration on main, then E2E and contract verification).
AI-written summary · about
chapters (21)
- 0:00Introduction
- 2:22Bugs
- 4:37Common bug causes
- 6:14Software development life cycle
- 8:08Testing pyramid
- 9:24Testing trophy
- 11:03Microservices
- 13:07Test Driven Development
- 14:23Go
- 16:40Fuzzing
- 18:33Third party APIs
- 19:24Copenhagen Devfest
- 24:30Integration vs Endtoend tests
- 26:42HTTP Test Library
- 27:43Test Containers Project
- 29:16Integration Testing
- 37:14Contract Testing
- 40:47Contract Test
- 45:36GitHub Actions
- 50:39Summary
- 52:10Questions
related talks
31mBuilding a microservices architecture with Go
42mBoosting Test Coverage for Microservices
02h 36mTesting Java Microservice
57mEnd-to-End Automated Testing in a Microservices Architecture
40mBoosting test coverage for microservices
47mDev/Testing challenges with microservices and CD
38mMicroservices in Go using Micro
45mBuilding a successful test automation architecture in a microservices environment