From REST to Events: API Workflow Testing & Mocking with a Single Arazzo Spec
summary
Demonstrates an end-to-end workflow proof: author an intent, auto-generate an Arazzo specification that stitches OpenAPI and AsyncAPI steps, then run a Docker+Kafka mock and generate tests with Specmatic to exercise both the “products available” and “empty list” paths. The demo shows mocks and tests running together (closed‑loop), exposes missing features (no SOAP support, no per-item looping yet), and successfully simulates multi-step sync+async journeys.
AI-written summary · about
chapters (13)
- 0:00Workflows and Arazzo intro
- 1:54Demo coverage
- 2:36Order workflow example
- 4:02Sync and async workflows
- 5:07Workflow in Specmatic
- 6:51OpenAPI and AsyncAPI specs
- 8:40Visual workflow stitching
- 10:08Arazzo spec generation
- 12:36Arazzo spec structure
- 14:22Sync and async steps
- 14:43Closed loop tests with mocks
- 17:33Summary
- 17:54Q&A
related talks
33mKafka and JMS Mocking with AsyncAPI using Specmatic
24mUsing API spec as an Executable Contract To Mock and Test Microservices
30mBreak the API Test Data Bottleneck: Real Scenarios on Real Systems
31mBeyond OpenAPI: API Workflows That AI Agents Can Actually Execute
51mFramework agnostic REST api testing
35mFake It Before You Make It: Mocking Your Way to Better HTTP APIs
37mStop Doing E2E Tests! Write Better Tests with Contract
43mImprove your API and OpenAPI