Contract testing with examples or Contract First
summary
Shows how to use API specification formats RAML and Swagger to make REST-based mobile/web client-server testing clearer, helping decide whether a bug is in client or server. Demonstrates using specs to simplify manual testing in Postman, and automating contract tests with tools Dredd and Abao, plus how to set up a contract-testing process.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:25Quality expectations
- 5:33What is contract testing
- 7:21Contract First in teams
- 8:25Specification as truth
- 10:32REST API contract elements
- 14:04Contract formats
- 16:10Benefits of contracts
- 19:19Writing contract tests
- 21:28Reducing test duplication
- 23:38Contract testing tools
- 25:05Summary
- 26:12Q&A
related talks
23mContract Testing for Mobile Application Development
50mRun Specs & Avoid Wrecks — A "Speed With Seatbelts" Lab
37mStop Doing E2E Tests! Write Better Tests with Contract
32mGetting started with Rest APIs
39mConsumer-Driven Contract Testing With Postman
20mOpenAPIspec
51mContract-Driven Development-Escape Microservices Integration & Deployment Hell
35mContract Testing and Laravel: Reliability in APIs Between Microservices