Here’s an example implementation of the second use case using Selenium’s JavaScript language bindings: import * as assert from 'node:assert' These problems can’t be solved using WebDriver Classic because it’s not bidirectional. Another use case is that you may wish to write an automated test to check that a web page logs a warning or throws an exception when intended.

# Logging powered by WebDriver BiDiĪ common use case is to automatically verify that a web page loads without any console logs, warnings, or errors and without any uncaught JavaScript exceptions. Since then, WebDriver BiDi gained adoption in popular frameworks, addressing top developer pain points by unlocking highly requested features such as logging support. In 2022, both Chrome/ChromeDriver 106 and Firefox 102 shipped support for the WebDriver BiDi standard. The WebDriver BiDi effort involves standardization work, the creation of Web Platform Tests, and implementations for different browser engines. The best of both worlds! Read A look back in time: the evolution of test automation and WebDriver BiDi - the future of cross-browser automation for more background. That’s why in 2020, the W3C Browser Testing and Tools Working Group began work on WebDriver BiDi, a new standard browser automation protocol that bridges the gap between the WebDriver Classic and CDP protocols. In contrast, CDP is more efficient and powerful, but less interoperable. There are some fundamental differences between these two protocols: WebDriver is an interoperable standard, but the protocol is less efficient and lacks features that CDP has.

WebDriver is a browser automation protocol, defined as a W3C standard, with implementations in ChromeDriver, GeckoDriver, and WebKitDriver.Ĭhromium also has its own proprietary browser automation protocol: the Chrome DevTools Protocol, or CDP. This article gives an overview of what’s new in WebDriver BiDi in 2023. How to Manually Update Your Chrome Extensions

Upgrade chrome