Beyond WebDriver!
summary
WebDriver moves from request/response to a persistent, event-driven protocol called WebDriver BiDi that opens a WebSocket JSON‑RPC‑ish channel so tests can receive DOM mutation events, JavaScript error logs and limited network info while preserving existing synchronous APIs for easy migration. It aims for cross‑browser interoperability (Google, Mozilla, Microsoft driving the spec) and automation-first features similar to CDP/Puppeteer but with security and scale concerns — sending logs from lots of browsers can overload runners; demos run up to 200 concurrent sessions.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:39Welcome
- 1:38Agenda
- 2:08The Past
- 7:05The Good Bad
- 11:15The Future
- 12:14WebDriver Baidai
- 16:55Use Cases
- 19:45Problems
- 22:00Opportunities
- 23:16Next Steps
- 24:36Questions
related talks
31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and...- 31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium
24mWebDriver BiDi: work in progress.
26mHow browser automation works behind the scenes
11mThe Future of Cross-Browser Automation: WebDriver BiDi
01h 26mWorkshop: Reactive Browser Testing with WebDriver BiDi
42mAdvancing WebDriver BiDi support in WebKit
15mBrowser automation/testing with BiDi and minimal dependencies