WebdriverIO + Puppeteer. Double Gun – Double Fun
summary
Compare the W3C WebDriver HTTP protocol (used by tools like WebdriverIO) with the Chrome DevTools Protocol used by Puppeteer, explaining each protocol’s strengths (WebDriver’s widespread support vs. Puppeteer’s WebSocket two-way communication and browser event subscriptions). Demonstrate experiments combining WebdriverIO and Puppeteer in a single project so tests can use both protocols and leverage the best features of each to control the browser.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:17WebDriver overview
- 9:21Chrome DevTools Protocol
- 14:39WebSocket for Puppeteer
- 18:12Puppeteer via WebSocket
- 20:18Merging WebDriver & Puppeteer
- 23:49Dual browser connection
- 26:42Benefits of dual control
- 28:51CSS/JS coverage metrics
- 30:57HTTP request interception
- 33:24Puppeteer events
- 35:54Selenium Grid integration
- 37:20Demo dual connection
- 38:25Protractor implementation
- 40:53Puppeteer browser support
- 42:22Future prospects
- 43:09Summary
related talks
48mWebdriverIO + Puppeteer. Double gun - double fun
43mPuppeteer Is the New WebDriver? Secrets of Flawless Testing
26mHow browser automation works behind the scenes
33mBeyond WebDriver!
31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium
44mWebdriverIO: The next-gen automation test framework you should know about
01h 02mModern web testing and automation with Puppeteer
30mModern Web Testing and Automation with Puppeteer