How to Save Time Analyzing Load Test Reports
summary
Shows an approach for analyzing large volumes of load-testing results to save time when tests produce many metrics per scenario and have hundreds of tested functions and multiple variants and load levels. Describes techniques to detect what changed versus the previous day and attribute causes without re-running tests, aimed at nonfunctional (performance) testing and dashboard/graph automation for faster triage.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 4:30Load report analysis problem
- 6:17Visualization vs text
- 7:50Avoiding averages
- 9:41Avoiding medians
- 11:53Faster graph analysis
- 12:16Test result requirements
- 14:08Metric scoring index
- 16:20Ranking and index formula
- 19:10Single result graph
- 21:37Automating analysis
- 22:25Tools and technologies
- 26:06Implementation results
- 34:58Q&A
related talks
10mHow to Use Small Load Tests? | Performance vs Load Testing
46mLoad Testing Without Being Off the Mark
50mFrom Load Testing to Reliability Engineering: Making Performance Testing Predict Production Behavior
47mQuality Control for High-Load Systems
51mLoad Testing: How to Know Your Limits
26mLoad testing websites following the steps of a user journey
53mEarly Performance Testing: Finding News You Can Use
44mPerformance Testing: the way to make a true load