Contract-Driven API Development with OpenAPI Specification
summary
Argues OpenAPI as a true contract that prevents drift by failing CI when code and spec diverge, and shows a concrete workflow: spec in its own repo, review branch, generate docs, pull a version into implementation for contract testing with the Ruby committee validator, lint with Spectral, mock with Stoplight and run a local mock server using Prism for consumer tests. Demonstrates dynamic mocking, generated clients, and how this cuts late-stage surprises and broken integrations.
AI-written summary · about
chapters (13)
- 0:00Introduction to API challenges
- 3:35Traditional API development issues
- 6:02OpenAPI specification overview
- 11:01Benefits of OpenAPI design
- 12:47Contract testing with OpenAPI
- 15:44Design-first vs code-first process
- 19:14Kalanley's implementation process
- 20:44Using Stoplight Studio editor
- 23:11Documentation and mocking features
- 26:25Client-side mocking with Prism
- 29:38Contract testing on both sides
- 30:22Process benefits summary
- 31:26Q&A session
related talks
20mOpenAPIspec
50mContract-Driven Development
27m"Building Elegant API Contracts: From Zero to Hero"
43mWhy You Should Be Doing Contract-First Development
19mSecure and accelerate APIs' lifecycle with the OpenAPI specification
26mBuilding APIs for Developers & Machines
37mAutomation++ - Building an Enterprise API Economy from scratch
30mOne Spec to Rule them all - OpenAPI in Action