Easier Adoption of Contract Testing With Bidirectional Contracts
summary
Demonstrates that bi‑directional contracts let consumer and provider each upload their own contract to Pact Flow and the broker compares them automatically, finding a real mismatch: one consumer expects HTTP 200 on delete while the provider (and another consumer) returns 204. Shows consumer contracts from Pact, provider contracts from an OpenAPI spec, and contracts generated from existing integration tests using WireMock. Verification results publish immediately to the broker so deployments can be gated and the mismatch is detected by the tooling.
AI-written summary · about
chapters (9)
- 0:00Introduction to contract testing
- 3:06Distributed systems challenges
- 7:02Contract testing benefits
- 10:12Consumer driven contracts
- 14:33Live demo setup
- 27:34Implementation challenges
- 31:26Introduction to bi-directional contract testing
- 33:53Bidirectional contracts demo
- 41:45Q&A
related talks
09m"Contract Testing 101"
32mConsumer-Driven Contract: A better approach for API Testing
22mCollaborating with Contracts
30mReliable End to End Testing with API Contracts using Cypress & Pactflow
59mUsing Pact to Deploy Microservice with Confidence
42mInvestigating Contract Testing
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
23mContract Testing for Mobile Application Development