Jenkins pipeline integration in Selenium Java - Test Execution Trace

Test Overview

This test automates a login page using Selenium WebDriver in Java. It verifies that the login button is clickable and that the user is redirected to the dashboard page after login. The test is designed to be run in a Jenkins pipeline to ensure continuous integration.

Test Code - JUnit 5 with Selenium WebDriver

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.support.ui.ExpectedConditions;
import org.openqa.selenium.support.ui.WebDriverWait;
import org.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.assertEquals;

public class LoginTest {
    private WebDriver driver;
    private WebDriverWait wait;

    @BeforeEach
    public void setUp() {
        // Assuming chromedriver is in system PATH
        driver = new ChromeDriver();
        wait = new WebDriverWait(driver, 10);
    }

    @Test
    public void testLogin() {
        driver.get("https://example.com/login");

        WebElement usernameInput = wait.until(ExpectedConditions.presenceOfElementLocated(By.id("username")));
        WebElement passwordInput = driver.findElement(By.id("password"));
        WebElement loginButton = driver.findElement(By.id("loginBtn"));

        usernameInput.sendKeys("testuser");
        passwordInput.sendKeys("password123");

        wait.until(ExpectedConditions.elementToBeClickable(loginButton));
        loginButton.click();

        wait.until(ExpectedConditions.urlContains("/dashboard"));
        String currentUrl = driver.getCurrentUrl();
        assertEquals("https://example.com/dashboard", currentUrl);
    }

    @AfterEach
    public void tearDown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

Execution Trace - 9 Steps

Step	Action	System State	Assertion	Result
1	Test starts - JUnit initializes and runs testLogin method	No browser open yet	-	PASS
2	ChromeDriver instance created and browser window opens	Browser window is blank	-	PASS
3	Navigates to https://example.com/login	Login page is loaded with username, password fields and login button	Waits for presence of username input field	PASS
4	Finds username, password input fields and login button by their IDs	All elements are present on the page	-	PASS
5	Enters 'testuser' in username and 'password123' in password fields	Input fields filled with test credentials	-	PASS
6	Waits until login button is clickable	Login button is enabled and clickable	-	PASS
7	Clicks the login button	Browser sends login request	-	PASS
8	Waits until URL contains '/dashboard'	Page redirects to dashboard	Checks current URL equals 'https://example.com/dashboard'	PASS
9	Test completes and browser closes	Browser window closed	-	PASS

Failure Scenario

Failing Condition: Login button is not found or not clickable, or URL does not change to dashboard after login

Execution Trace Quiz - 3 Questions

What does the test verify after clicking the login button?

A That the URL changes to the dashboard page

B That the login button becomes disabled

C That the username field is cleared

D That an alert popup appears

Key Result

Use explicit waits like WebDriverWait with ExpectedConditions to handle dynamic page elements and avoid flaky tests in Jenkins pipelines.