Advanced Selenium 4.0 Framework Development with Junit5

Set up and run the jp store application by cloning the pet store project from GitHub, building the war file, and deploying to a local Tomcat server.

Install Docker on Windows by downloading Docker Desktop for Windows, meet Windows 10 64-bit Pro/Enterprise/Education requirements, restart to enable container features and verify with docker ps and docker run hello-world.

Install Docker Desktop on macOS by verifying hardware requirements, downloading the binary, signing into Docker Hub, and launching the application. Verify installation with docker --version and docker run hello-world.

Walk through the JPetStore demo, register and log in, browse products, add items to the cart, checkout with dummy data, view the health page, and review orders.

Download, extract, and organize all necessary browser drivers for Windows, including ChromeDriver, GeckoDriver, PhantomJS, Edge WebDriver, and IE driver, then add them to the system path and verify they run.

Download and unzip the macOS browser drivers (Chrome, Firefox, phantom), store them in a browsers folder, then add the folder to the path and verify access.

Create a new maven project, configure artifact coordinates and directories, and add JUnit 5 and Selenium dependencies along with surefire, allure, and maven compiler plugins for test execution and reporting.

In this lecture, set up the Selenium 4 project structure by creating packages for web driver, pages, steps, tags, and helpers, plus resources with data and drivers.

Create and execute your first selenium test with maven, configure ChromeDriver, and generate early reports using JUnit 5 annotations.

Configure allure to write results to target/allure-results by adding a property in the allure properties file, ensuring clean, fresh results with maven clean test, and generate the report under target.

Create a TestBase class to centralize setup and teardown in Selenium 4.0 JUnit 5 framework. Extend tests from this base to share the driver and avoid repeating initialization and cleanup.

Learn to assign meaningful display names to Selenium tests using JUnit 5 DisplayName and generators, including standard and replace underscores options, and understand precedence across method, class, and property levels.

Implement a property reader using the singleton design pattern with a private constructor, synchronised getInstance, and a volatile instance to read values from application properties for tests.

Store property keys as enum values to centralize strings and simplify refactoring; expose string values via a getter and use static imports in tests.

Learn to use WebDriverManager to auto-download and manage Chrome and Firefox executables, enabling seamless cross-browser testing with a property-driven switch between manager and local binaries.

Identifies design flaws in the test base, where driver creation and browser options are bundled together, causing static driver risks and flaky tests in parallel runs; proposes refactoring.

Design architecture for driver factory presents a setup with a browser type enum, setup interface for browser caps and options, and a driver manager handling initialization and cleanup with JUnit.

Create a driver setup interface for Selenium 4.0 with JUnit 5, defining methods to get browser capabilities, get browser options, and get web driver.

Create a browser type enum to manage Chrome and Firefox with a driver setup interface, building Chrome and Firefox options and capabilities for remote and local execution.

Create a thread-safe driver factory using ThreadLocal, with getDriver and quitDriver methods, an internal browser determiner from properties, and an enum of Chrome and Firefox that supplies browser-specific WebDriver configurations.

Create a driver manager class to handle setup and teardown of drivers in Selenium 4 JUnit 5, using before all, after all, before each, and after each with cookies cleanup.

Explore the page object model as a design pattern that centralizes UI locators. Reduce code duplication and simplify maintenance by updating a single page object's methods.

Walks through implementing a page object model in the project, defining a base page with common elements, and page-specific classes for login, dashboard, and products, plus a steps class.

Develop an HtmlPageObject class that uses By strategies (id, css, xpath, link text, etc.) with explicit waits and by-object overloads for single or multiple element retrieval.

Create a generic HtmlPageObject to interact with text boxes, buttons, links, dropdowns, and checkboxes using by locators or web elements, enabling enter, clear, click, get text, and verify page text.

Build a base page that centralizes common elements and metrics across login, dashboard, and product pages. Extend the page object for consistent navigation and interaction.

Continue building the base page by adding methods to click sign in, navigate the dashboard, access product and help pages, and support search and sign out with a category enum.

Build the login page object by modeling username, password, login button, and register link; implement a login method, navigate to registration, and retrieve invalid login messages using web elements.

Build an allure steps class to centralize page-object interactions, initialize pages once, and enrich test reports with steps like navigating the app and logging in with credentials.

Learn how to disable individual test methods or whole test classes using JUnit 5 annotations in the Selenium 4 framework, and compare per method and class level disabling.

Add hard and soft assertions to Selenium tests using JUnit 5, validate the dashboard greeting after login, and use soft assertions with lambdas to run multiple checks.

Organize nested test classes with the @Nested annotation in JUnit 5, validating invalid credentials and error messages while structuring tests under a parent login test.

Build account page objects in a Selenium 4 framework, implementing methods to enter user, account, and profile information, select by visible text, toggle checkboxes, and save to reach the dashboard.

Learn to create a user registration test that registers a new user, logs in, and verifies the welcome message, while avoiding hard-coded data with a fake data API.

Use the Java Faker API to replace hard-coded values with faker-generated data for user registration, creating a faker instance to populate names, emails, passwords, and addresses, and run Maven build.

Implement a public synchronized method to take a webpage screenshot, cast the driver to TakesScreenshot, obtain bytes, and attach the image to the Allure report, controlled by a screenshot property.

Learn to capture screenshots of a specific web element in selenium 4.0 with junit5, attach them to reports, and toggle element screenshots via a property.

Implement a JUnit 5 test listener to perform actions on test failure, success, or abort, using the extension context to access test details and capture screenshots.

Explore how to rerun flaky tests using the rerun Jupiter plugin in a Selenium 4 with JUnit 5 setup, including dependency installation, annotations, and guidance to investigate root causes.

Group tests by tags using JUnit 5 annotations, define tag constants, and run specific groups with Maven -D properties to execute smoke or regression tests.

Learn to enrich allure test steps by adding locator information using a log helper and a configurable switch, enabling detailed element and text interaction logs in selenium 4 with junit5.

Learn to drive parameterized testing in selenium 4 with JUnit 5 by reading user data from a CSV file and executing a registration test across multiple data rows.

Learn to implement data-driven tests with Apache POI by reading Excel data for Selenium 4 and JUnit 5. Build an Excel data reader that outputs a 2D array for tests.

Create a parameterized login test by reading username, password, and expected results from an Excel file with JUnit 5 method source, enabling multiple-user validation in a Selenium 4 framework.

Learn to execute tests in parallel with the Maven Surefire plugin, tuning parallel, thread count, and reuse/fork strategies for memory-efficient concurrency, with on-the-fly overrides via -D properties.

Explore implementing a system property helper to override Selenium test settings at runtime via mvn -D properties, enabling dynamic element screenshot control and on the fly configuration.