Load testing websites following the steps of a user journey
summary
Shows actual results and tradeoffs: J meter is the recommended starter tool, Locust lets teams generate far more traffic cheaply by leveraging cloud infra, and Blaze meter makes GUI tests roughly 100× more expensive than API tests. Concrete wins: moving from limited three-run vendor tests to daily open‑source runs cuts cost and increases coverage. Practical details: persist unique cookies, include realistic pauses, refresh test data, correlate load spikes with monitoring to find DB locks, CPU or third‑party bottlenecks.
AI-written summary · about
chapters (12)
- 0:00Load testing importance
- 1:52User journey in load testing
- 3:17Test user journeys vs random traffic
- 5:03Realistic test scenarios
- 7:07Frontend vs backend load testing
- 9:17Open source vs commercial tools
- 11:03Load testing evolution
- 13:10JMeter setup best practices
- 14:58Locust setup and reporting
- 16:47Preparation for load testing
- 17:31Tool recommendations
- 18:56Q&A
related talks
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things
46mLoad Testing Without Being Off the Mark
30mBeat the rush! Designing effective load tests for your web application
45mBeat the rush! Designing effective load tests for your web application
47mLoad Testing You Always Wanted
26mIntroduction to Load Testing
29mAzure Load Testing in action
51mLoad Testing: How to Know Your Limits