Testing Swagger Contracts without Contract Based Testing
summary
Shows a method for validating Swagger/OpenAPI API contracts without full contract-based testing frameworks by comparing Swagger/OpenAPI spec files. The approach generates JSON Schemas from Swagger JSON files and then compares those schemas against actual API responses to detect differences between spec and implementation.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:04API testing without docs
- 5:41Documentation relevance
- 8:33Nested data and errors
- 10:24Swagger testing needs
- 12:39Pact Contract Testing failed
- 17:03Validating schemas
- 19:55Generating JSON schemas
- 25:07Library issues
- 30:03Ignoring JSON keys
- 33:19Schema resolver
- 34:03CI/CD integration
- 35:51Not a silver bullet
- 37:19Summary
related talks
36mTesting via OpenAPI, or How to Validate Your Documentation
01h 21mContract Driven Development-Deploy MicroServices Independently W/out Integration Testing
37mContract testing with examples or Contract First
50mContract-Driven Development
01h 20mContract Driven Development-Deploying MicroServices Without Integration Testing
29mContract Testing in Python for a Data Science API
33mDynamic Test Generation with OpenAPI 3.0
34mAutotest Coverage Visualization
