Collaborating with Contracts
summary
Shows that consumer-driven contracts catch real breaks (removing a name field that still powers two consumers) and enable parallel work across many services by making expectations explicit and executable. Demonstrates the pact gem workflow: consumer tests run a mock server, emit a JSON pact, then pact verify fires real HTTP at the provider and runs full-stack checks. Describes provider states for setup (example: inserting 10,000 friends) and warns about how much to assert and integration with CI.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:52Real life collaboration
- 2:07Collaboration
- 3:56Consumer Different Contracts
- 6:54Why is this useful
- 7:40ConsumerDriven Contracts
- 8:44ConsumerDriven Contracts Workflow
- 13:54Packed
- 17:13Provided States
- 18:43Summary
- 19:15Questions
related talks
32mConsumer-Driven Contract: A better approach for API Testing
09m"Contract Testing 101"
39mPacts to the Rescue! Making your microservices play nicely together
45mDeploy microservices confidently using Consumer Driven Contracts
59mUsing Pact to Deploy Microservice with Confidence
01h 00mTesting Microservices and Evolving APIs with Consumer Driven Contracts
10mDeploy microservices confidently using Consumer Driven Contracts
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
