WebdriverIO + Puppeteer. Double gun - double fun
summary
Compares the W3C WebDriver HTTP protocol (used by tools like WebdriverIO, Selenide, Protractor) with Chrome DevTools Protocol accessed via Puppeteer. Demonstrates each protocol’s capabilities (WebDriver’s established ecosystem vs. Puppeteer’s WebSocket-based two-way communication and browser event subscription) and shows how to combine them in a single project to leverage strengths of both.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:36WebDriver history
- 3:03W3C WebDriver protocol
- 5:12How WebDriver controls browsers
- 9:03Chrome DevTools Protocol
- 13:20WebDriver vs DevTools Protocol
- 16:30Puppeteer overview
- 19:00WebDriver + Puppeteer idea
- 21:30Technical setup
- 25:46WebDriverIO integration
- 27:12Usage example
- 29:16Speed comparison
- 30:21Puppeteer testing features
- 32:09HTTP request interception
- 33:13File uploads in Puppeteer
- 34:18Selenium Grid scaling
- 36:50Puppeteer browser support
- 38:38Use cases
- 41:06When to use this combo
- 43:36Test speed impact
- 45:21Q&A
related talks
49mWebdriverIO + Puppeteer. Double Gun – Double Fun
43mPuppeteer Is the New WebDriver? Secrets of Flawless Testing
26mHow browser automation works behind the scenes
31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium
33mBeyond WebDriver!
30mModern Web Testing and Automation with Puppeteer
48mThe Nuts and Bolts of WebdriverIO
51mIs Puppeteer the New WebDriver? Secrets of Flawless Testing