Automated Performance Testing With WebDriver
summary
Shows concrete results and tools: WebDriver plus a Chrome devtools service captures trace events, Lighthouse and trace screenshots, and an assertion API that runs in CI. Reports use metrics like time to first byte and first contentful paint and cites 53% abandonment if load > 3s and average page loads ~3.2s. Demonstrates injecting slow scripts, a cloud-run open-source runner called Speedo, and a Jenkins-style jank check that measures frame drops and flags regressions.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:45Performance Matters
- 4:11Browser Performance Metrics
- 7:35User Experience Metrics
- 10:52Trace Logs
- 15:39WebDriver
- 23:58Cloud
- 26:25Speedo
- 33:03Jenkins
- 35:36Best Practices
related talks
43mAutomated Performance Testing With WebDriver
31mAutomated Performance Testing With WebDriver
25mAutomated Performance Testing With WebDriver
19mWorking Well: The Future of Web Testing
40mAutomated Performance Testing In Preproduction
35mWeb Application Performance Testing from Users Perspective
21mThe Future of Performance Tooling
26mAutomated Web Performance Testing Before 5pm