WebDriver
A RESTful HTTP interface specification formally standardized by the W3C in 2018, enabling test scripts to control browser behavior through browser driver programs. It serves as the underlying communication protocol for automated testing tools such as Selenium.
Core Facts
Timeline (last 90 days)
Communicating directly with the browser core (for example, via CDP or a custom IPC channel) can bypass the WebDriver protocol stack and reduce command latency by an order of magnitude.
The WebDriver protocol specifies that the client and the browser driver interact through HTTP request-response exchanges in JSON format.
Selenium was born in 2004 and has long relied on the WebDriver protocol to communicate with browsers via HTTP; this architecture leads to slow execution speeds and race conditions prone to occur during network fluctuations.
Selenium's traditional workflow requires installing three major components: the Selenium library, the target browser, and the corresponding browser driver (WebDriver).
Playwright, developed by Microsoft, integrates both the Chrome DevTools Protocol (CDP) and WebDriver control channels, supporting parallel execution across Chromium, Firefox, and WebKit.
WinAppDriver is from Microsoft and is a WebDriver-protocol-compatible service specifically designed to automate Windows desktop applications (including UWP and traditional Win32 applications), relying on Windows UI Automation technology to locate interface elements.
Appium is the de facto standard for mobile automated testing, extending the WebDriver protocol and adapting to different platforms through different drivers.
All Facts (10)
Selenium is the foundational framework for Web UI automation, controls browser behavior based on the WebDriver protocol, and supports multi-language bindings including Python and Java.
80%Unverified传统浏览器自动化工具基于WebDriver协议或CDP（Chrome DevTools Protocol）驱动浏览器，所有操作路径必须由开发者预先硬编码
90%UnverifiedSelenium is a browser automation framework originally designed for web application testing, capable of driving a real Chrome browser to execute page JavaScript and obtain cookies with a legitimate Token.
60%UnverifiedCommunicating directly with the browser core (for example, via CDP or a custom IPC channel) can bypass the WebDriver protocol stack and reduce command latency by an order of magnitude.
50%UnverifiedThe WebDriver protocol specifies that the client and the browser driver interact through HTTP request-response exchanges in JSON format.
50%UnverifiedSelenium was born in 2004 and has long relied on the WebDriver protocol to communicate with browsers via HTTP; this architecture leads to slow execution speeds and race conditions prone to occur during network fluctuations.
50%UnverifiedSelenium's traditional workflow requires installing three major components: the Selenium library, the target browser, and the corresponding browser driver (WebDriver).
50%UnverifiedPlaywright, developed by Microsoft, integrates both the Chrome DevTools Protocol (CDP) and WebDriver control channels, supporting parallel execution across Chromium, Firefox, and WebKit.
50%UnverifiedWinAppDriver is from Microsoft and is a WebDriver-protocol-compatible service specifically designed to automate Windows desktop applications (including UWP and traditional Win32 applications), relying on Windows UI Automation technology to locate interface elements.
50%UnverifiedAppium is the de facto standard for mobile automated testing, extending the WebDriver protocol and adapting to different platforms through different drivers.
50%