Automated Performance Testing In Preproduction
summary
Shows how to hook open source tools into CI to gate releases: spin up webpagetest on a staging build, run headless browsers (or Puppeteer/Selenium scripts) against realistic emulated networks, collect UX timings and user timings, run Lighthouse/PageSpeed/YSlow checks, store results (InfluxDB or HTTP Archive) and compare to historic baselines to detect regressions. Define absolute thresholds and performance budgets, run multiple iterations to avoid jitter, flag specific defects (huge assets, unoptimized media, blocking JS) and fail or annotate the build.
AI-written summary · about
chapters (5)
- 0:00Introduction and motivation
- 8:47Performance as a bug
- 18:40Metrics and budgets to track
- 26:28Automating with open source
- 37:44Implementation and summary
related talks
31mAutomated Performance Testing With WebDriver
37mAutomated Performance Testing With WebDriver
53mEarly Performance Testing: Finding News You Can Use
33mPerformance Testing in Agile and DevOps
29mProgressive Testing to Meet the Performance Imperative
01h 02mThe Art & Joy of Testing in Production
57mOpen Forum on Performance Testing
45mHow to Build a Performance Testing Pipeline from Scratch
