"Contract Testing 101"
summary
Explains that consumer-driven contract testing uses Pact to record JSON contracts from consumer tests, spin up a mock provider during consumer CI, then push contracts to a Pact Broker so providers can verify against real service behavior. Describes the Pact CLI’s can-i-deploy check, type matching to ignore value churn, and faster, isolated feedback loops. Notes limits: needs cross-team buy-in, breaks for public or third‑party APIs, and does not replace functional or performance testing.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:54Isolated tests
- 3:05API integration tests
- 4:19Contract testing
- 5:12Pact
- 5:43Consumer
- 6:11Provider
- 6:34Benefits
related talks
32mConsumer-Driven Contract: A better approach for API Testing
23mContract Testing for Mobile Application Development
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
59mUsing Pact to Deploy Microservice with Confidence
22mContract Testing – An efficient way for integration testing
01h 00mTesting Microservices and Evolving APIs with Consumer Driven Contracts
47mContract-Based Testing for Microservices and UI
22mCollaborating with Contracts