About
The Spring Boot of Selenium
Selenium Boot lets teams focus on testing, not framework engineering.
Vision
Testing should be about test intent — not the plumbing underneath it. We want a world where a Java team can add one dependency and immediately have a maintained, parallel-safe, well-documented automation foundation, instead of rebuilding one at every company.
Why it exists
Almost every Java team writes its own BaseTest,DriverFactory, and pile of wait utilities — unpaid infrastructure they own, debug, and maintain forever, rarely tested or parallel-safe. Selenium Boot is that framework, built once and maintained for everyone: sensible defaults, Playwright-inspired ergonomics, and enterprise features — without ever hiding Selenium.
Design principles
- · Zero boilerplate — if it takes more than one line to enable, it should be a default.
- · Convention over configuration — smart defaults, optional YAML for the rest.
- · No required external services — the core works offline.
- · Never hide Selenium — drop to raw WebDriver whenever you need to.
- · A single dependency — add
selenium-bootand nothing else.
Who it's for
- · Teams maintaining a home-grown framework — keep your test intent, delete the plumbing you rewrite at every company.
- · Teams already invested in Selenium — get Playwright-inspired ergonomics without leaving Selenium, Java, or your Grid.
- · Engineering leads — parallel-safe by default, CI pass-rate gates, maintained and tested for you.
- · AI-assisted teams — the MCP server generates framework-native, accessibility-first tests from a recorded session.
By the numbers
Part of the Selenium ecosystem
Selenium Boot is listed among the test frameworks on theSelenium project's ecosystem page. It builds on Selenium WebDriver rather than replacing it, and it is an independent project — a listing there is not an endorsement by the Selenium project.
Maintainers & license
Selenium Boot is open source under the Apache-2.0 license, created and maintained by its author and a growing community of contributors. Contributions are welcome — see thecontributing guideand community page.
Get in touch: hello@seleniumboot.com· report a vulnerability privately atsecurity@seleniumboot.com.
Keep your test code. Delete the plumbing.
Add one dependency and focus on testing — not framework engineering.
<dependency>
<groupId>io.github.seleniumboot</groupId>
<artifactId>selenium-boot</artifactId>
<version>3.9.0</version>
</dependency>Or start from a working project:use the starter template ↗