Basics of GraphQL and Testing GraphQL APIs
summary
Claims that GraphQL returns “nothing more nothing less,” exposes a single super endpoint and usually replies 200 even on logical failures, and demonstrates testing with Postman and JavaScript plus a tv4 schema check. Concrete recommendations: treat response shape per-request with schema validation, assert error node presence instead of HTTP codes, design tests by business flows, cover request permutations and key-ordering. Two audience polls report ~72% and ~57% agreement on expected behaviors, and a BFF wrapper migration pattern proves practical.
AI-written summary · about
chapters (14)
- 0:00GraphQL basics
- 1:04What GraphQL is
- 3:52APIs vs GraphQL analogy
- 8:51REST vs GraphQL requests
- 15:49GraphQL query poll
- 19:20REST vs GraphQL differences
- 21:04Testing GraphQL APIs
- 27:20Schema validation
- 31:32HTTP response codes
- 32:57Test cases by function
- 37:03Testing permutations
- 40:53GraphQL vs REST
- 42:38API choice poll
- 47:09Key takeaways and Q&A session
related talks
32mTesting GraphQL APIs
19mFunctional Testing of GraphQL APIs: Simple Checks That Catch Real Bugs
41mTesting GraphQL: From Zero To Hundred Percent
18mBreaking the Mold Innovative Approaches to Testing GraphQL APIs
08mFast 'End-to-End' Testing with GraphQL
38mPerformance Testing sucks! How to get started testing RESTful APIs and GraphQL
48mGraphQL Is the New Sexy
31mStop Guessing A11y: Auto-Generate Playwright Tests from Your GraphQL Schema