Selenide

Visit Website

Introduction

Selenide is a framework for writing easy-to-read and easy-to-maintain automated UI tests in Java. It sits on top of Selenium WebDriver (version 4 and later) and replaces most of the boilerplate around it: starting and closing the browser, waiting for elements, taking screenshots on failure and writing assertions.

The API is built around the $ and $$ functions. $("#submit").click() finds and clicks an element, and $("#username").shouldHave(text("Hello, Johny!")) asserts on it. Every should condition waits until it becomes true or a timeout passes, which the project describes as doing ‘some magic for ajax-based applications’. In practice this removes most explicit waits and many of the flaky failures that come with them.

Because Selenide is a thin layer over WebDriver, it runs wherever Selenium runs: local browsers, Selenium Grid and cloud grids. The README points to plugins for Appium (mobile), Moon and Selenoid containers, Selenium Grid and video recording, and recent versions also document an MCP setup so AI coding agents can use Selenide.

Selenide works with JUnit 5, JUnit 4 and TestNG, and keeps WebDriver available for anything it does not wrap. On failure it automatically saves a screenshot and the page source, which makes CI failures much easier to diagnose than a bare stack trace.

In the quality loop, Selenide belongs at the end-to-end and functional stage for Java teams. It is especially popular with teams that already have Selenium knowledge and infrastructure but want shorter, more stable tests without moving to a different automation engine.

The source code is at selenide/selenide on GitHub under the MIT licence, with about 1,900 stars; the most recent commit was on 9 November 2026.

Features

1. Concise $ API: Find, act and assert in one line with $, $$ and fluent conditions such as shouldBe(visible).
2. Automatic waiting: Every condition retries until it passes or times out, so explicit waits are rarely needed.
3. Browser lifecycle: Selenide opens, reuses and closes the browser for you; no WebDriver setup code in each test.
4. Screenshots and page source: Saved automatically when a test fails, with links in the report.
5. Collections: $$ handles lists of elements with conditions such as shouldHave(size(3)) or texts(...).
6. Selenium compatible: Built on Selenium WebDriver 4+, so it works with Grid and cloud providers and you can still reach the raw driver.
7. Test framework support: Works with JUnit 5, JUnit 4 and TestNG.
8. Plugins: Official plugins for Appium, Selenoid, Moon, Selenium Grid and video recording.
9. Page objects: Supports classic page objects as well as simple ‘page component’ classes built from $ fields.
10. Configuration: Browser, timeout, base URL and reporting options via code, system properties or a properties file.

Pros

1. Less flaky tests: Built-in waiting removes a common source of timing failures in Selenium suites.
2. Gentle learning curve: Teams that know Selenium become productive quickly.
3. Free to use: Open source under the MIT licence, so the core tool costs nothing to use.
4. Actively maintained: The repository had commits as recent as 9 November 2026.

Cons

1. Java only: Selenide is for JVM languages; other stacks need a different tool.
2. Inherits WebDriver limits: Network interception and multi-tab handling are not as rich as in CDP-based tools like Playwright.
3. Smaller community: About 1,900 GitHub stars, so fewer answers online than for plain Selenium.
4. Global state: The static $ style is convenient but can be awkward in heavily parallel or multi-browser tests.

Usage and Links (Example)

Add Selenide to a Gradle or Maven project:

testImplementation 'com.codeborne:selenide:7.19.1'

A JUnit 5 test:

import static com.codeborne.selenide.Selenide.*;
import static com.codeborne.selenide.Condition.*;

class LoginTest {
  @Test
  void userCanLogIn() {
    open("https://example.com/login");
    $("#email").setValue("user@example.com");
    $("#password").setValue(System.getenv("TEST_PASSWORD")).pressEnter();
    $(".welcome").shouldHave(text("Welcome"));
  }
}

Practical tips:

1. Set Configuration.baseUrl and Configuration.timeout once in a base class instead of per test.
2. Use Configuration.remote to point at Selenium Grid or a cloud grid in CI.
3. Keep screenshots and page sources as CI artifacts; they are the fastest way to debug a red build.
4. Prefer shouldHave/shouldBe over manual Thread.sleep or WebDriverWait calls.

Resources:

• Selenide website
• GitHub repository

Pricing

Selenide is free and open source under the MIT licence.

Recommended for?

1. Java teams already using Selenium who want shorter, more stable tests.
2. Organisations with Selenium Grid infrastructure that want to keep it.
3. QA engineers new to automation, thanks to the small, readable API.
4. Not a fit for non-JVM stacks, or if you need deep network control that CDP-based tools offer.

Conclusion

Selenide is a mature, focused improvement on raw Selenium WebDriver for Java. Its automatic waiting, concise syntax and built-in diagnostics fix many day-to-day pains of browser testing.

If your team is committed to the JVM and WebDriver, it is one of the easiest ways to make an existing suite more reliable without changing infrastructure.

On CheckOps, Selenide is filed under the End-to-end & functional stage. Related tools listed here include Selenium, Serenity BDD, Playwright, Geb, Atata and WebDriverIO. Before choosing, compare them on licence, supported languages and platforms, hosting model, and how well each fits your existing CI pipeline. Facts on this page were checked against the official website, documentation and repository on 11 November 2026; statements the vendor makes about its own product are marked as vendor claims.