Modern web testing and automation with Puppeteer
summary
Explains Puppeteer’s concrete wins: six lines of Node code launch Chrome, scrape Joel’s t‑shirt price, and a browser context isolates tests and claims up to 100× faster than full relaunches; announces puppeteer Firefox with ~90% API parity; demos request interception for server mocking and “catify” images, service‑worker inspection and evaluation, accessibility snapshots, tracing and coverage, and a Lambda packaging option (Chrome AWS Lambda ~34 MB) that runs headless in CI.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:57What is Puppeteer?
- 7:50Web Testing Challenges
- 12:13Tests are Flaky
- 16:18Recap
- 21:58Navigation Tracking
- 23:15Evaluation
- 24:58Test Isolation
- 29:34Modern Web
- 31:53Device Emulation
- 32:31Offline Emulation
- 34:27Service Workers
- 37:35Geolocation: London
- 39:42Network Monitoring
- 43:38Performance Testing
- 46:32Code Coverage
- 46:56Accessibility API
- 49:46Accessibility Visualizer
- 50:41Community
related talks
30mModern Web Testing and Automation with Puppeteer
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
46mWhen Tests Met Puppeteer
27mI Like to Puppeteer
43mPuppeteer Is the New WebDriver? Secrets of Flawless Testing
01h 15mPuppeteer can automate that!
32mEnd to End tests with Google's Puppeteer