Browserless Testing in Vaadin 25

Use the Vaadin MCP tools (search_vaadin_docs, get_component_java_api) to look up the latest documentation whenever uncertain about a specific API detail. Always set vaadin_version to "25" and ui_language to "java".

The docs MCP doesn't cover the testing framework itself. For exact tester / ComponentQuery / @ViewPackages signatures or source, use the javadoc MCP (mcp__javadoc__* — find via ToolSearch javadoc if not loaded) against the com.vaadin:browserless-test-shared, browserless-test-junit6, and browserless-test-spring artifacts instead of unpacking jars from ~/.m2.

What Browserless Testing Is

Browserless tests (previously called "UI Unit Tests") run server-side Java code without a browser or servlet container. You interact directly with your server-side view classes and Vaadin components. The BrowserlessTest / SpringBrowserlessTest base classes set up the Vaadin session, UI, and routing — all in the same JVM as your JUnit tests.

This makes tests fast (milliseconds, not seconds), stable (no browser flakiness), and easy to run in CI.

Free for all users since Vaadin 25.1. Earlier versions required a commercial TestBench subscription.

When to Use Browserless Tests vs. End-to-End Tests