Performance Testing sucks! How to get started testing RESTful APIs and GraphQL
summary
Shows concrete workflows: use StormForger or generators like JMeter and Gatling to run scripted journeys (human id 14 example) and compare five REST calls versus one GraphQL query; measure 99th percentile latencies not averages. Demonstrates a non‑functional goal of <1s and films <500ms, but test run hits 1800ms so requirements fail. Reveals caching hit‑rate, long‑URL and gateway isolation issues and that fixing one layer requires re‑run and deeper tracing.
AI-written summary · about
chapters (35)
- 0:00Intro
- 0:39Title
- 1:08Lars
- 2:04REST API
- 2:37What is REST
- 3:58Rest
- 4:59Kraft Girl
- 5:18Facebook Supercraft
- 5:55GraphQL Query Language
- 7:57GraphQL is the new REST
- 9:27Performance Testing
- 9:57Performance Problems
- 11:16What is Performance Testing
- 12:10Stress Testing
- 13:05What do we have to do
- 14:29Low generators
- 14:56Who is in the situation
- 15:36Lets do this
- 15:58Setting test goals
- 17:03Test case definition
- 17:25JavaScript DSL
- 18:20Test run
- 18:50Reports
- 21:19Problem
- 22:16Isolation
- 23:32Regrets
- 24:54Hit Rate
- 26:00Optimizations
- 26:47Routing
- 27:22Complete Guide
- 27:54restful or craft
- 28:12when to choose
- 29:02what should you do
- 29:55what is the problem
- 31:41discussion drive
related talks
19mFunctional Testing of GraphQL APIs: Simple Checks That Catch Real Bugs
32mTesting GraphQL APIs
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things
41mTesting GraphQL: From Zero To Hundred Percent
08mFast 'End-to-End' Testing with GraphQL
35mLoad Testing Made Easy with Gatling
01h 10mPerformance Testing Crash Course
52mBasics of GraphQL and Testing GraphQL APIs