JUnit 5

Introduction

JUnit 5 is a practical Selenium skill for engineers converting working Selenium scripts into reliable test suites. Instead of learning it as a command, learn the release problem it solves, the failure it prevents, and the framework decision behind it.

Purpose of this lesson

Story: A QA team had 400 tests but no listener, no retry policy, and no report screenshots. Every red build became a detective story. In this lesson, jUnit 5 gives modern lifecycle hooks, extensions, and IDE-friendly test execution. The goal is to make Selenium feel like engineering, not record-and-playback automation.

Understanding the topic

Why this exists: JUnit 5 gives modern lifecycle hooks, extensions, and IDE-friendly test execution. Test frameworks provide lifecycle, data, assertions, parallelism, listeners, retries, and reports around Selenium's browser control.

• Real problem solved: JUnit 5 reduces manual regression cost, flaky feedback, or debugging ambiguity.
• Production use: TestNG/JUnit suites, CI pipelines, reporting, retries, parallel execution, and release gates.
• Beginner misuse: Putting driver setup, test data, assertions, and reporting inside every test class.
• Expert move: Use framework hooks to collect evidence and manage lifecycle, not to hide business logic.

Visual explanation

Mental model:

Test runner
  ↓
Hooks / fixtures
  ↓
Driver lifecycle
  ↓
Test method
  ↓
Listener evidence

Informative example

A practical Java + Selenium example for JUnit 5:

@AfterMethod
public void captureFailure(ITestResult result) {
    if (!result.isSuccess()) {
        screenshots.save(driver, result.getName() + "-junit-5.png");
    }
}

Execution workflow

Real-world use

In real teams, JUnit 5 becomes valuable when it gives a trustworthy signal under product change. The lesson is not “how to use one API”; it is how to design a check that survives browser differences, frontend re-renders, test data changes, and CI timing pressure.

Best practices

• Separate setup/teardown from test intent.
• Use listeners for screenshots and logs.
• Use data providers for meaningful variation.
• Track retries as flakiness, not success.

Common mistakes

• Retrying every failure without classification.
• Parallelizing before driver and data are thread-safe.
• Using hard assertions where soft assertions would show all field failures.

Debugging tips

• Check listener output before rerunning locally.
• For parallel issues, inspect thread-local driver handling.
• If reports are unclear, add URL, screenshot, HTML, and browser logs.

Advanced interview questions

Summary

JUnit 5 becomes valuable when it protects a real release, shortens feedback, and stays maintainable as the product changes.