Avoiding Common Pitfalls With Modern Microservices Testing
summary
Microservices tests pass locally but the system still breaks because mocks lie; the session demonstrates a concrete fix using consumer-driven contract testing with Pact and a Pact broker to publish/verify pacts, running a mock server on localhost:8096 and verifying provider behavior so mismatches (null color, 204 vs 404/500) surface before deploy. The live Wookie carpet demo shows CI green services but broken integration and how publishing a pact makes provider tests fail until the implementation or contract is corrected.
AI-written summary · about
chapters (11)
- 0:00Introduction to microservices testing
- 4:03Why testing matters in microservices
- 9:01Testing complexity in distributed systems
- 15:49Documentation pitfalls and testing
- 20:25Demo: Testing gone wrong
- 26:29Contract testing explained
- 31:26Pact contract testing deep dive
- 41:05Consumer-driven contract testing
- 56:12Fixing broken contracts
- 58:16Future of Pact and Quarkus
- 1:01:07Q&A and closing remarks
related talks
24mHow to test microservices and stay sane
01h 21mMicro-Service Delivery Without the Pitfalls
39mWhy you should contract test your Microservices 🧭
39mPacts to the Rescue! Making your microservices play nicely together
22mMicro Testing Pains
59mUsing Pact to Deploy Microservice with Confidence
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
47mContract-Based Testing for Microservices and UI