Why CI integration enables continuous testing in Selenium Java - Test Execution Impact

Test Overview

This test checks that a simple web login page works correctly when run automatically in a Continuous Integration (CI) environment. It verifies that the login button is clickable and the login form is present, demonstrating how CI integration allows tests to run continuously and catch issues early.

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.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.*;

public class LoginPageCITest {
    private WebDriver driver;

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

    @Test
    public void testLoginButtonIsClickable() {
        driver.get("https://example.com/login");
        WebElement loginForm = driver.findElement(By.id("login-form"));
        assertNotNull(loginForm, "Login form should be present on the page");

        WebElement loginButton = driver.findElement(By.id("login-button"));
        assertTrue(loginButton.isDisplayed() && loginButton.isEnabled(), "Login button should be visible and enabled");

        loginButton.click();
        // Additional assertions could be added here for post-click behavior
    }

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

Execution Trace - 6 Steps

Step	Action	System State	Assertion	Result
1	Test starts and ChromeDriver is initialized	Chrome browser window opens controlled by Selenium WebDriver	-	PASS
2	Browser navigates to https://example.com/login	Login page loads with login form and login button visible	-	PASS
3	Find login form element by id 'login-form'	Login form element is located in the DOM	Assert login form is not null	PASS
4	Find login button element by id 'login-button'	Login button element is located and visible	Assert login button is displayed and enabled	PASS
5	Click the login button	Login button is clicked, triggering any client-side or server-side login action	-	PASS
6	Test ends and browser closes	Browser window closes, WebDriver quits	-	PASS

Failure Scenario

Failing Condition: Login button element is not found or not clickable

Execution Trace Quiz - 3 Questions

What does the test verify about the login button?

A That it changes color on hover

B That it is visible and enabled for clicking

C That it automatically logs in the user

D That it is disabled initially

Key Result

Integrating UI tests into CI pipelines ensures tests run automatically on every code change, catching UI problems early and improving software quality.