DevTools and Headless Chrome–The Automation Power-Couple
summary
Chrome 59 running headless Chrome with puppeteer automates real browser actions to extract data and measure runtime metrics. A scraper turns a schedule page into JSON; an unused‑CSS reporter uses DevTools Protocol commands (eg CSS.startRuleUsageTracking) to compute 14% unused after simulated clicks versus 54% on a straight load. The demos show exact protocol calls, the node code to launch Chrome, and CI‑ready checks that alert when CSS regressions occur — and they work as shown.
AI-written summary · about
chapters (7)
- 0:00Start
- 8:26Headless Chrome Works Really Well with Docker
- 8:42Chrome Dev Tools
- 12:35Flame Chart
- 14:06Launch Headless Chrome
- 18:13Coverage Panel
- 23:05Recap
related talks
31mDevTools and Headless Chrome - The Automation Power-Couple
32mDevTools and Headless Chrome - The Automation Power Couple
30mPowerful Automation with the Chrome DevTools Protocol
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
01h 15mPuppeteer can automate that!
31mThe Chrome DevTools Protocol!
30mExploring the Chrome Debugger Protocol for Test Authoring
20mGoing steady with the Chrome Dev Tools