How to Save Your APIs From DOOM
summary
Design-first OpenAPI definitions stored in SwaggerHub feed ReadyAPI to generate tests, mocks and CI commands; the demo uses Jeff Harris’s Restful Doom server so teams beat level one by scripting dozens of API actions from a text data source. ReadyAPI creates virtual services, runs data-driven loops with property expansion, and exports test runner CLI for pipelines. Workshops show the approach speeds test coverage and avoided “API doom” in practice, though a live run sometimes still dies.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 10:40SwaggerHub Overview
- 15:08ReadyAPI
- 17:00Create a new project
- 17:45Demo
- 20:50Project Coverage
- 21:55Striking Teams
- 23:15Swagger Hub
- 24:25AutoMock
- 26:15Mock API
- 29:20Swagger Hub Open API
- 30:20DOOM API Project
- 31:00DataDriven Testing
- 32:00Test Steps
- 34:10Data Source
- 34:50Data Source Example
- 37:10Questions
- 39:15Gameplay
- 44:00Usage Model
- 44:30Deployment Model
- 45:40GitHub Goal
- 48:55API Audience
related talks
19mSecure and accelerate APIs' lifecycle with the OpenAPI specification
16mAPI Platforms, Ready for Testing and Virtualization
27mGetting developers hooked on your API
05mAPI-First Development: Future-Ready Systems
44mCrafting Great APIs with Domain-Driven Design
37mAutomation++ - Building an Enterprise API Economy from scratch
35mFake It Before You Make It: Mocking Your Way to Better HTTP APIs
35mOpensource API Tools to agile your apifirst strategy.