DevTools and Headless Chrome - The Automation Power Couple
summary
Chrome runs headless (Chrome 59) and a small Node library controls it; use Puppeteer npm to launch Chrome, navigate, type credentials and scrape Meetup, take screenshots, or run tests inside Docker. The demo sends raw DevTools Protocol commands (CSS.startRuleUsageTracking / CSS.stopRuleUsageTracking) to compute unused CSS and flips from 54% -> 14% unused CSS after interacting with the UI. Output is a percentage that can trigger email/Slack alerts; it works. Headless Chrome (Chrome 59)
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:26Web automation overview
- 5:50Introducing Headless Chrome
- 6:57Puppeteer demo
- 12:50DevTools architecture
- 14:43DevTools protocol commands
- 17:48Running Headless Chrome
- 20:01Lighthouse and auditing
- 22:16Advanced protocol automation
- 30:50Summary and resources
related talks
19mDevTools and Headless Chrome - The Automation Power-Couple
25mDevTools and Headless Chrome–The Automation Power-Couple
30mPowerful Automation with the Chrome DevTools Protocol
31mThe Chrome DevTools Protocol!
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
01h 15mPuppeteer can automate that!
20mGoing steady with the Chrome Dev Tools
29mNext level of Front end testing with Devtools and WebDriver
