Revolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and...
summary
WebDriver BiDi promises a single, event-driven protocol that combines CDP’s low-level control with WebDriver’s cross‑browser reach, backed by Google, Microsoft, Mozilla and Apple and started at the W3C in 2020. It uses WebSocket bi-directional messaging, verifies implementations via web-platform-tests and a public dashboard (e.g. browsing context passes 444/482 in Chrome, network module 2/16 in Edge on Windows). A demo shows a real‑time console exception caught via the log inspector and the test passes; network interception remains unimplemented as of 15 Sep.
AI-written summary · about
chapters (13)
- 0:00Browser automation challenges
- 1:04Automation testing issues
- 2:08Browser automation history
- 3:54High-level vs low-level
- 6:43WebDriver Classic protocol
- 12:42Chrome DevTools Protocol
- 17:21Merging protocols into BiDi
- 19:30Implementing WebDriver BiDi
- 21:17Demo: real-time JS errors
- 23:46Network interception with BiDi
- 25:11Accessibility testing with BiDi
- 28:26BiDi future features
- 30:17Conclusion & Q&A
related talks
31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium
11mThe Future of Cross-Browser Automation: WebDriver BiDi
24mWebDriver BiDi: work in progress.
33mBeyond WebDriver!
42mAdvancing WebDriver BiDi support in WebKit
26mHow browser automation works behind the scenes
01h 26mWorkshop: Reactive Browser Testing with WebDriver BiDi
15mBrowser automation/testing with BiDi and minimal dependencies