ZuChromeDriver 0.8.2

ZuChromeDriver

Async .NET Chrome WebDriver and Chrome DevTools in one library. Connects directly to Chrome DevTools Protocol (CDP) over WebSocket — no separate chromedriver binary required.

ZuChromeDriver provides a Selenium-like WebDriver API (ZuWebDriver, By, WebElement) with an async-first contract (Task<T>). It also exposes full CDP access through the DevTools property.

Successor to AsyncChromeDriver with the same core idea: in-process CDP, chromedriver atom parity, and logic aligned with the reference Chromium Chromedriver implementation.

Solution layout

ZuChromeDriver.slnx
├── ZuChromeDriver/              # Main library (net10.0)
├── ChromeDevToolsClient/        # CDP transport (NuGet: Zu.ChromeDevToolsClient)
├── ChromeDevToolsClientGenerator/
├── HtmlForTests/                # Kestrel host for test pages
└── ZuChromeDriver.Tests/        # NUnit E2E against Chrome + HtmlForTests

Requirements

• .NET 10 SDK
• Google Chrome installed

Build

dotnet build ZuChromeDriver.slnx

Quick start

using Zu.Chrome;
using Zu.WebDriver;

var chrome = new ZuChromeDriver();
var driver = new ZuWebDriver(chrome);
await driver.GoToUrl("https://www.google.com/");

Headless Chrome

using Zu.Chrome;
using Zu.WebDriver;
using Zu.WebDriver.BasicTypes;

var config = new ChromeDriverConfig()
    .SetHeadless()
    .SetWindowSize(1280, 720);

var chrome = new ZuChromeDriver(config);
await chrome.Connect();
var driver = new ZuWebDriver(chrome);
await driver.GoToUrl("https://www.google.com/");
var screenshot = await driver.GetScreenshot();
var path = Path.Combine(Environment.CurrentDirectory, "google-headless.png");
await File.WriteAllBytesAsync(path, screenshot.AsByteArray);

Using DevTools directly

using Zu.Chrome;
using Zu.ChromeDevTools.Page;

var chrome = new ZuChromeDriver();
await chrome.Connect();
await chrome.DevTools.Page.Enable();
await chrome.DevTools.Page.Navigate(new NavigateCommand
{
    Url = "https://www.google.com/"
});

Domain adapters (Page, Runtime, DOM, Network, Input, …) are generated from the CDP schema in ChromeDevToolsClient.

FrameTracker

EnableFrameTrackerOnConnect defaults to false. Enable it when you need:

• SwitchTo().Frame(...) — execution context for iframes
• SwitchTo().Alert() — JavaScript dialog tracking via CDP

var config = new ChromeDriverConfig().SetEnableFrameTrackerOnConnect();

See ZuChromeDriver.Tests/README.md for test fixture patterns (RequiresFrameTracker, [NeedsFrameTracker]).

Running tests

Tests start HtmlForTests automatically on port 2310 and run E2E against a real Chrome instance.

dotnet test ZuChromeDriver.Tests\ZuChromeDriver.Tests.csproj

Filter a single fixture:

dotnet test ZuChromeDriver.Tests\ZuChromeDriver.Tests.csproj --filter "FullyQualifiedName~CookieImplementationTest"

Implementation status

Tests are ported from the Selenium .NET WebDriver test suite and run against HtmlForTests.

Documentation

Key types

License

Copyright (c) Oleg Zudov. Licensed under the Apache License, Version 2.0. See License.txt.

Portions are based on Selenium (Apache 2.0) and Chromium Chromedriver (BSD). See THIRD-PARTY-NOTICES.txt.