Investigating Contract Testing
summary
Compares concrete workflows: uses Spring Cloud Contract with Groovy/YAML-based contract files that generate producer-side tests and stubs, shows Pact Broker managing JSON pact artifacts in Docker for consumer-driven verification, and demonstrates Protocol Buffers as a compiled contract that generates language-specific classes so CI fails at compile time. Notes practical tradeoffs: Groovy DSL and language-specific pact generators cause friction, broker solves versioning, and protobuf catches many breaking changes earlier.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:56Contract Testing
- 9:13Consumer-Driven Contract
- 10:23Spring Cloud Contract
- 17:25Advantages and Pros and Cons of the Spring Cloud Contract
- 33:55Summary
related talks
09m"Contract Testing 101"
47mBeyond REST - Contract Testing in the Age of gRPC, Kafka & GraphQL
42mNonviolent Communication in the world of distributed systems
22mCollaborating with Contracts
59mUsing Pact to Deploy Microservice with Confidence
23mContract Testing for Mobile Application Development
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
43mEnhancing Backend Microservices Ecosystem with Contract Testing
