Contract Driven Development: The Death of Integration Hell
summary
Claims that executable API contracts replace most integration tests and remove "integration hell," demonstrated with the open‑source tool Qontract (contract.run). Contracts are authored in Gherkin, stored in a central Git repo, run as tests against provider APIs, and turned into wire‑compatible stubs for consumers to use for service virtualization. The workflow runs in CI, flags mismatched expectations, and blocks incompatible changes via backwards‑compatibility checks; supports REST/JSON, SOAP/XML and Kafka and lets teams independently deploy while catching integration breakage early.
AI-written summary · about
chapters (16)
- 0:00Contract driven development
- 4:36Speaker background
- 9:09Integration hell problem
- 11:57Shifting left with contracts
- 12:18Test pyramid and contract testing
- 22:57Why executable contracts
- 24:24Contract driven explained
- 27:16Collaborative contract authoring
- 28:19Contracts as tests
- 29:43Service virtualization
- 30:47Live demo: contract testing
- 37:47Consumer side stubbing
- 39:11Backward compatibility
- 42:02Protocols and tools
- 42:23Key takeaways
- 43:05Q&A
related talks
26mBuilding APIs for Developers & Machines
47mContract-Driven API Development with OpenAPI Specification
54mSolving challenges in API Testing to achieve more agile development
32mExtreme Contracts: the Freedom to Write the Tests you Need
35mTest automation guide: How to move away from chain tests
35mSolving challenges in API Testing to achieve more agile development
20mData Contracts: Keep Your Weekend Work-Free!
25mAdopting a Test driven Mindset in the Workplace