Selenium Boot

Selenium Boot

Java testing framework that brings Spring Boot conventions and Playwright APIs to Selenium

Open Source
4.9 (8 reviews)

Gallery

About Selenium Boot

Selenium Boot is a Java testing framework that simplifies browser automation by wrapping Selenium WebDriver with sensible defaults and modern APIs inspired by Playwright. The pitch is that you get enterprise grade automation without hiding Selenium underneath, so you keep the full power of the ecosystem while writing less boilerplate and fighting fewer timing bugs.

The biggest pain point it addresses is waiting. Anyone who has written Selenium tests knows the dance of Thread.sleep calls, explicit waits, and flaky assertions that pass locally but fail in CI. Selenium Boot centralizes all of that in a WaitEngine that auto waits before every action. You call a method, it waits until the element is ready, then acts. No manual sleep calls, no scattered WebDriverWait blocks.

Locators get the same treatment. Instead of chaining CSS selectors and XPaths that break every time the frontend team refactors a class name, Selenium Boot promotes accessibility first locators like getByRole, getByLabel, and getByText. These survive CSS refactors because they anchor to semantic attributes the user actually sees, not implementation details.

Assertions follow a web first model borrowed from Playwright. Instead of asserting immediately and failing if the condition isn't true yet, assertions auto retry until a timeout. If you're checking that a button becomes enabled after an AJAX call, the test waits for that state rather than throwing instantly. This one change eliminates a category of flakiness that plagues traditional Selenium suites.

On the reporting side, Selenium Boot generates HTML and JUnit XML reports out of the box. The HTML report includes a tabbed dashboard with test results, screenshots on failure, and step logs. CI systems like GitHub Actions, Jenkins, and GitLab are detected automatically, so environment variables and artifact paths just work without extra configuration.

For teams running tests in parallel, driver management is thread safe by default. You don't have to worry about one test closing the browser while another test is still using it. There's also global and per method retry logic for tests that are flaky due to external dependencies, with configurable retry counts.

Selenium Boot is free and open source under Apache 2.0. 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, this sits in a useful middle ground.

Key Features

  • Auto waiting actions via centralized WaitEngine
  • Accessibility first locators (getByRole, getByLabel, getByText)
  • Web first assertions that auto retry until timeout
  • Built in HTML and JUnit XML reporting
  • Thread safe driver management for parallel tests
  • Automatic CI detection for GitHub, Jenkins, GitLab

Pros & Cons

What we like

  • Eliminates manual Thread.sleep and explicit wait boilerplate
  • Locators survive CSS refactors by anchoring to semantic attributes
  • Auto retry assertions cut flaky test failures significantly
  • Free and open source under Apache 2.0

Room for improvement

  • Java only, not useful for Python or JavaScript test suites
  • Newer project with a smaller community than raw Selenium or Playwright
  • Learning curve if your team is used to raw WebDriver patterns
  • Documentation is still maturing

Frequently Asked Questions

What is Selenium Boot?
Selenium Boot is a Java testing framework that wraps Selenium WebDriver with auto waiting, accessibility first locators, and web first assertions. It aims to give you the reliability of Playwright style APIs while staying in the Selenium ecosystem.
Is Selenium Boot free?
Yes. It's open source under the Apache 2.0 license. There are no paid tiers or commercial restrictions.
Does Selenium Boot replace Selenium?
No. It builds on top of Selenium WebDriver, not around it. You still have access to the full Selenium API, but with convenience layers for waiting, locating, and asserting.
Who is Selenium Boot for?
Java teams writing browser automation tests who want to reduce boilerplate and test flakiness without migrating to a different framework. It's especially useful for teams with existing Selenium investments.

Best For

Building a new browser automation suite in Java without boilerplateReducing flakiness in an existing Selenium test suiteRunning parallel test execution with thread safe driver handlingGenerating CI friendly reports without custom scripting

Featured in

Alternatives to Selenium Boot

View all

Reviews (8)

Y
Yuki Pereira Verified

Recommended without reservation

Found Selenium Boot on a Show HN thread and I am glad I clicked. Where it really wins is free and open source under apache 2.0. The interface stays out of my way, which I appreciate. No regrets so far.

4/4/2026 12 found this helpful
T
Tao Singh Verified

Pulled its weight from week one

Tried Selenium Boot on a side project first, then rolled it out everywhere. Where it really wins is automatic ci detection for github, jenkins, gitlab. The thing I keep coming back to is how reliable it is. Glad I made the switch.

6/5/2026 7 found this helpful
A
Avery Davis Verified

Worth a look

Picked Selenium Boot for the price, stayed for the quality. Support actually answered when I had a question, which surprised me. It fits well for generating ci friendly reports without custom scripting. Recommending it to people in a similar spot.

6/23/2026 6 found this helpful
M
Mila Santos

Finally something that fits

Found Selenium Boot on a Show HN thread and I am glad I clicked. Their take on auto retry assertions cut flaky test failures significantly is genuinely good. The thing I keep coming back to is how reliable it is. Mostly using it for reducing flakiness in an existing selenium test suite.

6/16/2026 6 found this helpful
A
Amara Ramos Verified

Recommended without reservation

Three months of Selenium Boot later, here is what holds up. Where it really wins is auto retry assertions cut flaky test failures significantly. Found it works best for generating ci friendly reports without custom scripting.

6/14/2026 3 found this helpful
C
Chioma Singh

Worth a look

Three months of Selenium Boot later, here is what holds up. Got real value out of locators survive css refactors by anchoring to semantic attributes. Recommending it to people in a similar spot.

4/9/2026 3 found this helpful
L
Leon Tanaka

Pulled its weight from week one

Selenium Boot solves a real problem for me without making a fuss about it. What stands out is how it handles locators survive css refactors by anchoring to semantic attributes. It slotted into my routine without much fuss. Glad I made the switch.

6/2/2026 1 found this helpful
K
Krishna Lindqvist Verified

It just works

Hadn't planned on switching, but Selenium Boot was hard to ignore. Where it really wins is auto waiting actions via centralized waitengine. The interface stays out of my way, which I appreciate. Mostly using it for generating ci friendly reports without custom scripting. It earns its place in my stack.

6/8/2026