Why you should contract test your Microservices 🧭
summary
Argues that consumer-driven contract tests catch integration breakage on pull requests by generating a contract from unit-style consumer tests and replaying each interaction against the provider in CI, flagging breaking changes (example: age changed from integer to string). Uses Pact libraries to generate contracts and Pact Broker or Pactflow to publish and trigger provider verifications, runs verifications as GitHub Actions, and reduces costly end-to-end infra while keeping fast, deterministic checks.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:57Microservices Architecture Industry Examples
- 12:14Consumer Driven Contract Testing
- 13:17Generating the Contract(s): Consumer Tests
- 15:29Verifying the Contract: Provider Verification
- 17:56Need for Contract Testing in MicroServices
- 21:31Comparison with Unit & E2E Testing
- 28:56Pact Broker
- 33:13Connecting it all
- 34:20Closing Thoughts
related talks
43mEnhancing Backend Microservices Ecosystem with Contract Testing
24mHow to test microservices and stay sane
01h 21mMicro-Service Delivery Without the Pitfalls
01h 00mTesting Microservices and Evolving APIs with Consumer Driven Contracts
32mConsumer-Driven Contract: A better approach for API Testing
23mContract Testing for Mobile Application Development
22mContract Testing – An efficient way for integration testing
47mContract-Based Testing for Microservices and UI