Contract Driven Development-Deploy MicroServices Independently W/out Integration Testing
summary
Claim: API specs become executable contracts that let teams find compatibility bugs on laptops and in CI so integration environments stop blocking releases. The demo uses OpenAPI plus an open source tool Specmatic to auto-generate contract tests and smart mocks, producing ~42 generated tests then a later run that adds 16 more and exposes 26 failures (missing/nullable ID causing 500 instead of a 4xx). Workflow shows contract as stub for consumers, contract as test for providers, central git repo and semantic versioning to prevent breaking changes.
AI-written summary · about
chapters (21)
- 0:00Start
- 1:40Demo
- 1:54Open Api Specification
- 5:28Generative Tests
- 6:14Why Is this Test Failed
- 11:24Compatibility Issue
- 15:36Api Specifications into Executable Contracts
- 18:10The Open Api Specification Sample
- 20:36Postman
- 23:38Adding a Product
- 32:24Workflow Tests
- 34:20Set Expectations
- 36:22Anatomy of a Component Test
- 37:07Act Section
- 40:46Test First Development
- 41:38Specmatic Test
- 43:17Contract Tests
- 46:13Test Data Management
- 58:01Backward Compatibility
- 1:11:24Central Contract Repo
- 1:11:35Why Do We Need To Treat Contracts as Code
related talks
01h 20mContract Driven Development-Deploying MicroServices Without Integration Testing
51mContract-Driven Development-Escape Microservices Integration & Deployment Hell
50mContract-Driven Development
48mContract Driven Development: The Death of Integration Hell
49mCollaborative Contract Driven Development
01h 04mConsumer Driven Contracts and Your Microservice Architecture
45mContract Driven Development in AsyncApi
47mCollaborative Contract Driven Development