Powerful Automation with the Chrome DevTools Protocol
summary
Demos use Puppeteer against headless Chrome to automate real tasks: end to end tests that launch two browser instances to verify messaging, automated visual regression implemented in 20 lines of screenshot-and-compare code, prototype-based memory-leak detection that queries live objects, code-coverage export to Istanbul, and a screenshot/email reproduction service; all examples are built, runnable, and shown working against a simple chat app with reusable helper modules and CI-friendly setup.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:24Chat App
- 4:10Chrome DevTools Protocol
- 5:08What is the DevTools Protocol
- 7:13Setup
- 9:15Basic Test
- 11:32First Test
- 16:19Snapshot Testing
- 18:56Memory Leak Detection by Prototype
- 20:04Code Coverage
- 22:15MultiUser Testing
- 24:04Using Puppet to Build restful APIs
- 25:09Automating workflow with Puppet
- 27:06Testing with Puppet Recorder
- 28:35Outro
related talks
19mDevTools and Headless Chrome - The Automation Power-Couple
25mDevTools and Headless Chrome–The Automation Power-Couple
32mDevTools and Headless Chrome - The Automation Power Couple
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
31mThe Chrome DevTools Protocol!
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
30mExploring the Chrome Debugger Protocol for Test Authoring
46mWhen Tests Met Puppeteer