Adding Performance Assertion to Standard Functional Testing
summary
GoDaddy builds a small Node/Express webservice called cicd-perf-api that testers call from Selenium WebDriver: the service injects JavaScript that reads the browser W3C Performance API timestamps and resource timings, stores results in Elasticsearch + Kibana, and returns a boolean "assert" to fail CI when performance regresses. Teams spin it up with docker compose, use Python/JS clients, and report moving 75th‑percentile page loads from ~14–16s down to ~5–6s with revenue rising ~2.5×.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:24Marcels background
- 2:51What is web performance optimization
- 4:46Real user monitoring
- 10:49What did we learn
- 12:41Release
- 15:31Performance API
- 18:14Demo
- 22:35Python Test Script
- 28:55Live Demo
- 31:07Why opensource
- 35:22Page Load Waterfall
related talks
37mAutomated Performance Testing With WebDriver
40mAutomated Performance Testing In Preproduction
43mAutomated Performance Testing With WebDriver
29mProgressive Testing to Meet the Performance Imperative
28mPerformance is a Feature It Should Be Tested as Such
31mAutomated Performance Testing With WebDriver
25mAutomated Performance Testing With WebDriver
41mShift Left your Performance Testing