API testing journey through web protocols
summary
Five API styles share ~25% usage each so REST is not enough; the talk compares REST, SOAP, GraphQL, WebSockets and Webhooks with concrete testing implications: SOAP uses one POST endpoint and strict XML so focus on headers failures and structure, GraphQL returns JSON with 200-plus-error payloads so check errors inside responses not status codes, WebSockets need connectivity and long-lived message handling while Webhooks are one-way fire-and-forget; practical tools cited include Postman and Bruno and examples of broken servers and privacy bugs.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:10API protocols discussion
- 2:15API protocols overview
- 4:51REST misconceptions
- 5:57REST methods explained
- 9:37SOAP architecture
- 13:53SOAP testing strategies
- 14:15GraphQL fundamentals
- 17:48GraphQL errors and codes
- 18:51GraphQL query testing
- 20:35WebSockets for real-time API connections
- 22:23WebSocket testing
- 23:48Webhooks and events
- 25:33Q&A
- 27:59API testing problem
- 29:49Closing remarks
related talks
26mAutomate Your API Testing in CI/CD Pipelines
23mThe Why & How of Testing APIs
32mNavigating Modern API Platforms: Insights & Strategies
38mPerformance Testing sucks! How to get started testing RESTful APIs and GraphQL
28mTesting HTTP APIs in Ruby
04mSneak peek into the API world outside REST
45mFuzz Testing Web APIs: Overview of Existing Tools
51mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma