DevTools and Headless Chrome - The Automation Power-Couple
summary
Demos combining Chrome Headless and DevTools show concrete automation: launch headless Chrome, use Puppeteer to open pages, send raw DevTools protocol commands (via puppeteer.client.send) to enable CSS coverage, trigger interactions, then call startRuleUsage / stopRuleUsage and compute coverage. A scraper/test script reports precise numbers — e.g. 54% unused CSS with no interaction dropping to 14% unused CSS after exercising the UI — and the script runs and closes the browser successfully.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:45provide a good user experience in a consistent manner
- 1:12use a framework like selenium an end-to-end testing
- 4:47using the page dot evaluate method
- 13:15sending down the entire bootstrap css library to the client
- 13:45help us find the amount of unused css in your application
- 15:46using the network panel and the websockets filter
- 17:05start monitoring the css coverage
- 17:31add an event handler
- 17:51simulate all the user actions
related talks
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
19mWorking Well: The Future of Web Testing
01h 15mPuppeteer can automate that!
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
29mNext level of Front end testing with Devtools and WebDriver
25mAutomated Performance Testing With WebDriver
