~/talk

DevTools and Headless Chrome - The Automation Power-Couple

Talkat Render Conference 2018 · on Friday, 2018-03-23· [devops-and-delivery, testing]

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

  1. 0:00Start
  2. 0:45provide a good user experience in a consistent manner
  3. 1:12use a framework like selenium an end-to-end testing
  4. 4:47using the page dot evaluate method
  5. 13:15sending down the entire bootstrap css library to the client
  6. 13:45help us find the amount of unused css in your application
  7. 15:46using the network panel and the websockets filter
  8. 17:05start monitoring the css coverage
  9. 17:31add an event handler
  10. 17:51simulate all the user actions
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.