How to test microservices and stay sane
summary
Microservices cause flaky slow end to end suites so the team adopts consumer-driven contract tests with Pact to run consumer mocks and provider verifications instead of giant super end-to-end tests. Contracts are JSON files recorded by a mock server, uploaded to Pact Broker, and provider CI runs verifications that gate deployments. This finds concrete bugs like missing time zones for some countries and a typo that made an API return an empty array, letting the team cut E2E tests and speed CI.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:41What are microservices
- 3:10Testing monolith vs microservices
- 7:34Problems with super end-to-end tests
- 10:09What are contract tests
- 14:17Benefits of contract testing
- 21:46Pact Broker workflow
- 23:12Pact Broker overview
related talks
01h 21mMicro-Service Delivery Without the Pitfalls
01h 02mAvoiding Common Pitfalls With Modern Microservices Testing
39mPacts to the Rescue! Making your microservices play nicely together
39mWhy you should contract test your Microservices 🧭
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
47mContract-Based Testing for Microservices and UI
32mConsumer-Driven Contract: A better approach for API Testing
59mUsing Pact to Deploy Microservice with Confidence