Base page class pattern in Selenium Java - Test Execution Trace

Test Overview

This test uses the base page class pattern to open a web page, find a button, click it, and verify the resulting message is displayed correctly.

Test Code - JUnit 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.assertEquals;

// Base page class with common methods
class BasePage {
    protected WebDriver driver;

    public BasePage(WebDriver driver) {
        this.driver = driver;
    }

    public void click(By locator) {
        driver.findElement(locator).click();
    }

    public String getText(By locator) {
        return driver.findElement(locator).getText();
    }
}

// Home page class extending base page
class HomePage extends BasePage {
    private By buttonLocator = By.id("show-message-btn");
    private By messageLocator = By.id("message");

    public HomePage(WebDriver driver) {
        super(driver);
    }

    public void clickShowMessage() {
        click(buttonLocator);
    }

    public String getMessageText() {
        return getText(messageLocator);
    }
}

public class BasePagePatternTest {
    private WebDriver driver;
    private HomePage homePage;

    @BeforeEach
    public void setUp() {
        driver = new ChromeDriver();
        driver.get("https://example.com/testpage");
        homePage = new HomePage(driver);
    }

    @Test
    public void testShowMessageButton() {
        homePage.clickShowMessage();
        String message = homePage.getMessageText();
        assertEquals("Hello, World!", message);
    }

    @AfterEach
    public void tearDown() {
        driver.quit();
    }
}

Execution Trace - 7 Steps

Step	Action	System State	Assertion	Result
1	Test starts and Chrome browser opens	Browser window is open, ready to navigate	—	PASS
2	Browser navigates to https://example.com/testpage	Page loads with a button having id 'show-message-btn' and hidden message with id 'message'	—	PASS
3	HomePage object created with driver	Page elements accessible via HomePage methods	—	PASS
4	Clicks the button with id 'show-message-btn' using BasePage click method	Button is clicked, message becomes visible	—	PASS
5	Gets text from element with id 'message' using BasePage getText method	Message text is 'Hello, World!'	Verify message text equals 'Hello, World!'	PASS
6	Assertion checks if actual message text matches expected	Test verifies message correctness	assertEquals("Hello, World!", message) passes	PASS
7	Browser closes and test ends	Browser window closed	—	PASS

Failure Scenario

Failing Condition: Button with id 'show-message-btn' is missing or not clickable

Execution Trace Quiz - 3 Questions

What does the BasePage class provide in this test?

A Common methods to interact with web elements like click and getText

B The test assertions to verify results

C The browser driver setup and teardown

D The URL navigation logic

Key Result

Using a base page class helps reuse common web element actions, making tests cleaner and easier to maintain.

Practice

1. What is the main purpose of a BasePage class in Selenium Java testing?

easy

A. To define the main method for running tests

B. To store test data for different test cases

C. To group common web actions and avoid code repetition across page classes

D. To handle database connections during tests

Solution

1. Step 1: Understand the role of BasePage

   The BasePage class contains common methods like click, type, and wait that many page classes use.

2. Step 2: Identify the benefit

   By grouping these common actions, BasePage helps avoid repeating the same code in every page class.

3. Final Answer:

   To group common web actions and avoid code repetition across page classes -> Option C

4. Quick Check:

   BasePage groups common actions = A [OK]

Hint: BasePage holds shared actions to reuse in all pages [OK]

Common Mistakes:

• Confusing BasePage with test data storage
• Thinking BasePage runs tests directly
• Mixing BasePage with database handling

2. Which of the following is the correct way to declare a BasePage class constructor that accepts a WebDriver instance in Java?

easy

A. public BasePage(WebDriver driver) { this.driver = driver; }

B. public void BasePage(WebDriver driver) { this.driver = driver; }

C. BasePage(WebDriver driver) { driver = this.driver; }

D. public BasePage() { WebDriver driver; }

Solution

1. Step 1: Identify correct constructor syntax

   In Java, constructors have no return type and match the class name exactly.

2. Step 2: Check parameter assignment

   The constructor should assign the passed driver to the class field using this.driver = driver;.

3. Final Answer:

   public BasePage(WebDriver driver) { this.driver = driver; } -> Option A

4. Quick Check:

   Constructor no return + this.driver = driver [OK]

Hint: Constructor has no return type and uses this.driver = driver [OK]

Common Mistakes:

• Adding void return type to constructor
• Reversing assignment order
• Declaring driver inside constructor without class field

3. Given the following BasePage method, what will be the output if the element is not found within 5 seconds?

public void clickElement(By locator) {
  WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(5));
  wait.until(ExpectedConditions.elementToBeClickable(locator)).click();
  System.out.println("Clicked successfully");
}

medium

A. Prints 'Clicked successfully' after clicking the element

B. Prints 'Clicked successfully' immediately without waiting

C. Throws NoSuchElementException and prints 'Clicked successfully'

D. Throws TimeoutException and does not print anything

Solution

1. Step 1: Understand WebDriverWait behavior

   The wait.until waits up to 5 seconds for the element to be clickable.

2. Step 2: Outcome if element not found

   If the element is not clickable within 5 seconds, wait.until throws a TimeoutException and the click and print statements are skipped.

3. Final Answer:

   Throws TimeoutException and does not print anything -> Option D

4. Quick Check:

   Wait fails = TimeoutException, no print [OK]

Hint: Wait throws TimeoutException if element not clickable in time [OK]

Common Mistakes:

• Assuming print runs even if element not found
• Confusing TimeoutException with NoSuchElementException
• Thinking click happens immediately without wait

4. Identify the error in this BasePage method and how to fix it:

public void enterText(By locator, String text) {
  WebElement element = driver.findElement(locator);
  element.sendKeys();
}

medium

A. sendKeys() is missing the text argument; fix by adding sendKeys(text)

B. findElement should be replaced with findElements

C. Method should return boolean indicating success

D. Locator type By is incorrect; use String instead

Solution

1. Step 1: Check sendKeys usage

   The sendKeys method requires a String argument to input text.

2. Step 2: Fix the method call

   Change element.sendKeys(); to element.sendKeys(text); to send the provided text.

3. Final Answer:

   sendKeys() is missing the text argument; fix by adding sendKeys(text) -> Option A

4. Quick Check:

   sendKeys needs text argument [OK]

Hint: sendKeys always needs the text argument [OK]

Common Mistakes:

• Calling sendKeys without arguments
• Using findElements instead of findElement for single element
• Changing locator type incorrectly

5. You have a BasePage with a method public boolean isElementVisible(By locator) that returns true if element is visible. How would you use this method in a LoginPage class to verify the login button is visible before clicking it?

hard

A. if (isElementVisible()) { clickElement(loginButtonLocator); }

B. if (isElementVisible(loginButtonLocator)) { clickElement(loginButtonLocator); }

C. clickElement(loginButtonLocator); isElementVisible(loginButtonLocator);

D. isElementVisible(loginButtonLocator); clickElement();

Solution

1. Step 1: Use isElementVisible with locator argument

   The method requires a By locator to check visibility, so pass loginButtonLocator.

2. Step 2: Conditionally click if visible

   Use an if statement to call clickElement(loginButtonLocator) only if the element is visible.

3. Final Answer:

   if (isElementVisible(loginButtonLocator)) { clickElement(loginButtonLocator); } -> Option B

4. Quick Check:

   Check visibility with locator before click [OK]

Hint: Check visibility with locator before clicking [OK]

Common Mistakes:

• Calling isElementVisible without locator argument
• Clicking without checking visibility
• Calling clickElement without locator