Which WebDriver implementation claims to be the fastest?

HtmlUnitDriver claims to be the fastest WebDriver implementation in Selenium.

Why HtmlUnitDriver is fastest:

• ✓It does NOT launch an actual browser — it runs entirely in memory (JVM)
• ✓Uses HtmlUnit — a headless Java-based browser that simulates browser behavior
• ✓No GUI rendering, no graphics processing, no window management
• ✓Pure Java execution — no inter-process communication with an external driver

Usage:

import org.openqa.selenium.htmlunit.HtmlUnitDriver;

// Basic HtmlUnitDriver
WebDriver driver = new HtmlUnitDriver();

// With JavaScript enabled
HtmlUnitDriver driver = new HtmlUnitDriver(true);

// With specific browser version simulation
HtmlUnitDriver driver = new HtmlUnitDriver(BrowserVersion.CHROME);
driver.setJavascriptEnabled(true);

Comparison of driver speed:

HtmlUnit limitations:

• ✓JavaScript support is limited/simulated (not a real JS engine like V8/SpiderMonkey)
• ✓May not behave identically to real browsers for complex JS frameworks
• ✓Modern SPAs (React, Angular, Vue) may not work correctly
• ✓CSS rendering is simulated, not pixel-accurate

Modern headless alternatives (faster than HtmlUnit for real apps):

// Headless Chrome — fast AND real browser behavior
ChromeOptions options = new ChromeOptions();
options.addArguments("--headless=new");
WebDriver driver = new ChromeDriver(options);

// Headless Firefox
FirefoxOptions options = new FirefoxOptions();
options.addArguments("-headless");
WebDriver driver = new FirefoxDriver(options);

Key point: The fastest implementation is HtmlUnitDriver because it does not execute tests in an actual browser — it simulates browser behavior in pure Java without launching any browser process.