Selenium Boot

Selenium Boot is a Java testing framework that bills itself as the Spring Boot of browser automation. It wraps Selenium WebDriver with sensible defaults and modern APIs borrowed from Playwright, so teams get enterprise-grade test infrastructure without hiding the underlying Selenium engine. You keep full access to the ecosystem, the drivers, the community knowledge, while spending far less time on boilerplate configuration and flaky timing bugs.

The biggest pain point it tackles is waiting. Anyone who has maintained a Selenium suite knows the pattern. You pepper tests with Thread.sleep calls, scatter WebDriverWait blocks everywhere, and still watch green tests turn red in CI because the element wasn't quite ready when the script clicked it. Selenium Boot centralizes all of that in a WaitEngine that auto-waits before every action. The engine checks more than ten built-in conditions, from element visibility to text presence to interactability, and only proceeds once they pass. No manual polling, no arbitrary sleeps, just actions that wait for the browser to catch up.

Locators get the same treatment. Instead of chaining brittle CSS selectors and XPath expressions that break every time the frontend team refactors a class name or shuffles the DOM, Selenium Boot pushes accessibility-first locators like getByRole, getByLabel, getByText, and getByTestId. These target the accessibility tree rather than raw HTML structure, so they survive UI redesigns as long as the semantic meaning of elements stays intact. It's the same philosophy Playwright evangelizes, now available without leaving the Selenium world.

Assertions follow what the team calls a web-first model. Instead of asserting immediately and failing if the condition isn't true yet, each assertion auto-retries until a timeout. If you're checking that a submit button becomes enabled after an AJAX call, the assertion waits for that state rather than throwing instantly. This single change eliminates an entire category of flakiness that traditional Selenium suites struggle with, especially under the variable timing of CI environments.

Parallel execution is thread-safe by default. A ThreadLocal DriverManager isolates one driver per thread, so you can scale tests across methods or classes through configuration without worrying about one test closing a browser that another test is still using. Retry mechanisms are built in at three levels. You can mark methods with a Retryable annotation, hook global retries via a RetryListener, or quarantine flaky scenarios so they still run and report without failing the overall suite. Teams that inherit legacy tests can stabilize their builds without deleting flaky cases outright.

Reporting ships out of the box. The HTML dashboard presents a tabbed interface with an overview, individual test cases, failure details, and a flakiness radar that highlights tests with inconsistent results over time. JUnit XML output is generated alongside, compatible with any CI system that consumes standard test reports. GitHub Actions, Jenkins, and GitLab are detected automatically through a CiEnvironmentDetector that forces headless mode, tunes thread counts, and enforces configurable pass-rate gates when running in those environments.

Installation is a single Maven dependency from Maven Central. You add io.github.seleniumboot selenium-boot to your pom.xml, extend BaseTest or BasePage, and the lifecycle management, waits, retries, and reporting come along automatically. Configuration follows convention over configuration principles, with an optional selenium-boot.yml file for overrides and sensible defaults for everything else. Java 17 or later is required, and the framework supports both TestNG and JUnit 5 as test runners.

Beyond the core library, Selenium Boot offers an MCP server package on PyPI that enables AI-assisted test generation through Claude or Copilot. IDE plugins exist for IntelliJ IDEA (2024.2 and later via JetBrains Marketplace) and VS Code, providing in-editor assistance for writing and running tests. Documentation lives at docs.seleniumboot.com with a GitHub repository hosting discussions and example projects.

Selenium Boot is free and open source under the Apache 2.0 license. It targets Java teams that want to stay in the Selenium ecosystem but reduce the maintenance overhead of custom wait utilities, base classes, and reporting scripts. If you're starting a new automation project or inheriting a brittle test suite and looking for a path that doesn't require a full rewrite to Playwright or Cypress, this sits in a practical middle ground. You get modern ergonomics while preserving all the Java, Maven, and Selenium muscle memory your team already has.