Automated browser testing

Speedwave provides native browser automation capabilities, enabling Claude to drive an automated Chromium instance: rendering pages, interacting with forms, capturing screenshots, inspecting the accessibility tree, and validating visual assertions. This functionality is delivered via Microsoft’s official @playwright/mcp integration worker. See Web automation for integration options.

Appropriate use cases

Standard HTTP requests efficiently retrieve static documentation and server-rendered HTML. Browser automation should be used when inspecting dynamic single-page applications (SPAs), validating client-side JavaScript rendering, or capturing rendered layout snapshots.

Tip

For static web pages, API documentation, and Markdown repositories, prefer standard web fetching. Browser automation allocates full browser engine resources and should be reserved for interactive or client-rendered workloads.

Automated browser capabilities

The Playwright worker exposes tools categorized into four core domains:

• Navigation: Loading URLs, history navigation, and managing browser tabs.
• Data extraction: Generating accessibility tree snapshots, capturing full-page or element screenshots, and inspecting console output and network telemetry.
• Interactive actions: Clicking elements, typing text inputs, submitting forms, selecting dropdowns, simulating keystrokes, hovering, and dragging.
• Assertions and locators: Verifying element visibility, asserting text presence, and generating robust CSS/XPath locators.

Screenshots and rendered DOM structures are returned inline in tool responses rather than persisting unnecessary cache files to your workspace directory. See Data and privacy for data boundary details.

Local application testing

Because the browser engine executes within an isolated container, localhost resolves to the container network namespace. To test local development servers running on your host machine, target host.docker.internal in your requests (for example, http://host.docker.internal:3000 or http://host.docker.internal:4200).

Stateless session isolation

Each test invocation initializes an isolated, ephemeral browser profile. Local storage, indexed databases, and session cookies are cleared upon session completion, ensuring tests execute with complete isolation.

The browser worker container implements the standard Speedwave security baseline: dropped Linux capabilities, disabled privilege escalation, read-only root filesystems, and execution-disabled temporary storage. See the Isolation model for network constraints.