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.

Practice

1. What is the main benefit of integrating Continuous Integration (CI) with automated testing?

easy

A. Developers write tests manually after each release

B. Tests run automatically on every code change to catch bugs early

C. Tests are only run once before the final product launch

D. CI integration slows down the development process

Solution

1. Step 1: Understand CI integration purpose

   CI integration automates running tests whenever code changes are made.

2. Step 2: Identify the benefit of automation

   This automation helps find bugs early and reduces manual testing effort.

3. Final Answer:

   Tests run automatically on every code change to catch bugs early -> Option B

4. Quick Check:

   CI automation = early bug detection [OK]

Hint: CI runs tests on every change to catch bugs fast [OK]

Common Mistakes:

• Thinking tests run only at the end
• Believing CI slows development
• Assuming manual testing is always needed

2. Which of the following is the correct way to trigger a Selenium test in a CI pipeline using Java?

easy

A. Manually open the browser and run tests

B. Use java -jar selenium-server.jar without test classes

C. Run the test class with mvn test command

D. Write tests in Python and run with python test.py

Solution

1. Step 1: Identify standard Java test execution in CI

   Maven command mvn test runs Java Selenium tests automatically.

2. Step 2: Eliminate incorrect options

   Manual browser opening is not automated; running selenium-server alone doesn't run tests; Python command is unrelated to Java tests.

3. Final Answer:

   Run the test class with mvn test command -> Option C

4. Quick Check:

   Java tests run with mvn test [OK]

Hint: Use mvn test to run Java Selenium tests in CI [OK]

Common Mistakes:

• Confusing manual and automated test runs
• Using wrong commands for Java tests
• Mixing languages in CI commands

3. Given the following CI pipeline snippet triggering Selenium tests, what will happen if a test fails?

stage('Test') {
  steps {
    sh 'mvn test'
  }
}

medium

A. The pipeline will stop and mark the build as failed

B. The pipeline will ignore the failure and continue

C. The tests will rerun automatically until they pass

D. The pipeline will skip the test stage entirely

Solution

1. Step 1: Understand Maven test behavior in CI

   If any test fails, mvn test returns a failure exit code.

2. Step 2: Effect on CI pipeline

   CI pipelines stop on failure exit codes and mark the build as failed to alert developers.

3. Final Answer:

   The pipeline will stop and mark the build as failed -> Option A

4. Quick Check:

   Test failure = pipeline failure [OK]

Hint: Failed tests stop CI build immediately [OK]

Common Mistakes:

• Assuming tests auto-retry on failure
• Thinking pipeline ignores test failures
• Believing tests run without stopping pipeline

4. You integrated Selenium tests in your CI pipeline, but tests are not running after code commits. What is the most likely cause?

medium

A. The Selenium WebDriver is outdated but tests still run

B. Tests are passing too quickly to be noticed

C. The code commits are not triggering any build

D. The test stage is missing or not configured in the CI pipeline

Solution

1. Step 1: Check CI pipeline configuration

   If the test stage is missing or misconfigured, tests won't run after commits.

2. Step 2: Rule out other causes

   Passing tests still run; outdated WebDriver causes failures, not silence; commits usually trigger builds unless disabled.

3. Final Answer:

   The test stage is missing or not configured in the CI pipeline -> Option D

4. Quick Check:

   Missing test stage = no tests run [OK]

Hint: Verify test stage exists in CI config [OK]

Common Mistakes:

• Ignoring pipeline config errors
• Assuming tests run without pipeline setup
• Blaming WebDriver without errors

5. How does integrating Selenium tests into a CI pipeline improve software delivery speed and quality?

hard

A. By running tests automatically on every commit, catching bugs early and reducing manual testing delays

B. By requiring developers to manually trigger tests after each feature is complete

C. By running tests only once before the final release to save time

D. By replacing all manual testing with automated tests without human review

Solution

1. Step 1: Understand CI and Selenium test integration

   Automated tests run on every commit, providing quick feedback on code quality.

2. Step 2: Benefits of early bug detection and automation

   This reduces delays from manual testing and prevents bugs from reaching production.

3. Final Answer:

   By running tests automatically on every commit, catching bugs early and reducing manual testing delays -> Option A

4. Quick Check:

   Auto tests + early bugs = faster, better delivery [OK]

Hint: Auto tests on commits catch bugs early, speeding delivery [OK]

Common Mistakes:

• Thinking tests run only at release
• Believing manual triggers are needed
• Assuming automation removes all human checks