
Why Contract Testing Exists and Core Concepts

#184 - Contract Testing Essentials: A Comprehensive Guide - Lewis Prescott
Topic 2 of 9
Published Jul 22, 2024 · Clip 4:58–18:35 (13:37)
Lewis explains why contract testing exists: integration and API tests are flaky because they depend on environments, and breaking API changes are hard to identify. He describes the components—consumer, provider, contract, broker, and a CLI tool like can-i-deploy—and how contracts formed from request/response pairs are generated by consumers, stored centrally, and replayed by providers. The discussion covers shared understanding across teams, human error in maintaining specs in wikis, and the benefits: fast independent feedback, easier debugging, consumer-driven realism, and confident independent deploys verified via can-i-deploy.