Contract Driven Development-Deploying MicroServices Without Integration Testing
summary
Demo shows how an OpenAPI file becomes executable checks and stubs: Specmatic generates contract tests from the spec, flips a flag to run 26 additional negative cases, and serves high‑fidelity stubs that refuse inputs not matching the schema. JUnit support runs contracts-as-tests to drive provider code, examples guide stubbed values to avoid 500s, and a repo + specmatic.json pattern keeps a single source of truth. They add contract vs contract checks for backward compatibility and CI gates to catch API signature drift early.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:10Joel Rosario
- 1:40Demo
- 1:52Sample Application
- 2:31Contract Tests
- 15:31Open Api
- 22:46Change to the Contract
- 26:02Service Virtualization
- 39:24Anatomy of a Test
- 40:20Parts to a Component Test
- 46:01The Contract as a Test Approach
- 56:14The Api Design
- 1:00:53Recap
- 1:03:24Backward Compatibility
- 1:12:09What Happens if the Specifications Are Not Backward Compatible
- 1:17:26How Can We Embrace Contract Driven Development and How Does It Affect Your Ci Pipeline
- 1:19:15Qa
related talks
01h 21mContract Driven Development-Deploy MicroServices Independently W/out Integration Testing
51mContract-Driven Development-Escape Microservices Integration & Deployment Hell
50mContract-Driven Development
24mUsing API spec as an Executable Contract To Mock and Test Microservices
01h 04mConsumer Driven Contracts and Your Microservice Architecture
48mContract Driven Development: The Death of Integration Hell
49mCollaborative Contract Driven Development
45mContract Driven Development in AsyncApi