JUnit 5 Support

Selenium Boot supports both TestNG (built-in) and JUnit 5 (opt-in). The JUnit 5 integration provides the same lifecycle — driver management, HTML report, step timeline, screenshots, AI failure analysis, tracing, and flakiness tracking — with zero configuration beyond adding the dependency.

---

Setup

pom.xml

<dependency>
    <groupId>io.github.seleniumboot</groupId>
    <artifactId>selenium-boot</artifactId>
    <version>2.4.0</version>
</dependency>

<dependency>
    <groupId>org.junit.jupiter</groupId>
    <artifactId>junit-jupiter</artifactId>
    <version>5.10.2</version>
    <scope>test</scope>
</dependency>
<dependency>
    <groupId>org.junit.platform</groupId>
    <artifactId>junit-platform-launcher</artifactId>
    <version>1.10.2</version>
    <scope>test</scope>
</dependency>

No extra Surefire configuration needed — Maven Surefire 3.x auto-detects JUnit 5.

---

Option A — Extend BaseJUnit5Test

The simplest approach. Identical to extending BaseTest in TestNG:

class LoginTest extends BaseJUnit5Test {

    @Test
    void validLogin() {
        open();
        step("Enter credentials");
        $("input#username").type("admin");
        $("input#password").type("secret");
        $("button[type='submit']").click();

        step("Verify dashboard", true);
        assertThat(By.id("dashboard")).isVisible();
    }
}

BaseJUnit5Test provides: getDriver(), getWait(), open(), open(path), $(), assertThat(), step().

---

Option B — @EnableSeleniumBoot

Composed annotation for your own base class:

@EnableSeleniumBoot
abstract class AppTest {
    protected WebDriver getDriver() { return DriverManager.getDriver(); }
}

---

Option C — Parameter injection

No base class needed. Inject WebDriver directly into test methods:

@ExtendWith(SeleniumBootExtension.class)
class LoginTest {

    @Test
    void validLogin(WebDriver driver) {
        driver.get("https://example.com/login");
        driver.findElement(By.id("username")).sendKeys("admin");
        driver.findElement(By.cssSelector("button[type='submit']")).click();
    }
}

---

@PreCondition — Session caching

Use @PreCondition on a method or class to run a named setup step once and cache the session (cookies + localStorage). Subsequent tests with the same condition name restore the cached session instead of repeating the setup.

class DashboardTest extends BaseJUnit5Test {

    @Test
    @PreCondition("loginAsAdmin")
    @DisplayName("View dashboard — session restored, no re-login")
    void viewDashboard() {
        open("/dashboard");
        assertThat(By.id("welcome-header")).isVisible();
    }

    @Test
    @PreCondition("loginAsAdmin")
    @DisplayName("Edit profile — same cached session reused")
    void editProfile() {
        open("/profile");
        assertThat(By.id("profile-form")).isVisible();
    }
}

Apply to a class to cover all its test methods:

@PreCondition("loginAsAdmin")
class AdminTest extends BaseJUnit5Test {
    @Test void viewUsers() { ... }
    @Test void viewReports() { ... }
}

The condition provider lives in a BaseConditions subclass registered via SPI — same as TestNG:

public class AppConditions extends BaseConditions {

    @ConditionProvider("loginAsAdmin")
    public void loginAsAdmin() {
        open("/");
        new LoginPage(getDriver()).login("admin", "secret");
    }
}

src/test/resources/META-INF/services/com.seleniumboot.precondition.BaseConditions
→ com.yourcompany.conditions.AppConditions

On retry, the cached session is automatically invalidated and the provider reruns fresh.

---

Retry

Use @Retryable on a method or class. The framework retries with a fresh driver on each attempt:

class LoginTest extends BaseJUnit5Test {

    @Test
    @Retryable(maxAttempts = 1)   // 1 retry = 2 total runs
    void flakyLogin() {
        open();
        new LoginPage(getDriver()).login("admin", "secret");
        assertThat(By.id("dashboard")).isVisible();
    }
}

Place @Retryable on the class to apply to all its test methods:

@Retryable(maxAttempts = 2)
class FlakyTest extends BaseJUnit5Test { ... }

maxAttempts overrides the global retry.maxAttempts from selenium-boot.yml. Omit it to use the config value:

selenium-boot.yml

retry:
  enabled: true
  maxAttempts: 1

Retried tests show a ↻ Nx badge in the HTML report.

---

Parallel execution

src/test/resources/junit-platform.properties

junit.jupiter.execution.parallel.enabled=true
junit.jupiter.execution.parallel.mode.default=concurrent
junit.jupiter.execution.parallel.config.strategy=fixed
junit.jupiter.execution.parallel.config.fixed.parallelism=4

ThreadLocal driver isolation makes all three options thread-safe.

---

Feature parity with TestNG

Feature	Status
Auto driver provisioning	✅
selenium-boot.yml config	✅
Parallel execution	✅
WaitEngine	✅
BasePage	✅
StepLogger / step()	✅
HTML report + step timeline	✅
Screenshot on failure	✅
AI failure analysis	✅
Trace viewer	✅
Self-healing locators	✅
Fluent Locator API $()	✅
Web-first assertions assertThat()	✅
Network mocking	✅
Visual regression	✅
Flakiness prediction	✅
Video recording	✅
JUnit XML output	Native
@Retryable retry	✅
@PreCondition session cache	✅