Page class design in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium Page Object method?

Consider this Java Selenium Page Object method that returns the page title. What will be the output if the page title is "Welcome Page"?

Selenium Java

public class HomePage {
    private WebDriver driver;

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

    public String getPageTitle() {
        return driver.getTitle();
    }
}

// Assume driver.getTitle() returns "Welcome Page"

A "Welcome Page"

B "homepage"

C null

D Throws NoSuchElementException

💡 Hint

Think about what driver.getTitle() returns in Selenium.

The getPageTitle() method calls driver.getTitle(), which returns the current page's title as a string. Since the page title is "Welcome Page", the method returns that exact string.

❓ assertion

intermediate

Which assertion correctly verifies the presence of a button in a Page Object?

You have a Page Object with a method isSubmitButtonDisplayed() that returns a boolean. Which assertion correctly checks that the submit button is visible?

Selenium Java

public class LoginPage {
    private WebDriver driver;
    private By submitButton = By.id("submit");

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

    public boolean isSubmitButtonDisplayed() {
        return driver.findElement(submitButton).isDisplayed();
    }
}

A assertTrue(loginPage.isSubmitButtonDisplayed());

B assertFalse(loginPage.isSubmitButtonDisplayed());

C assertNull(loginPage.isSubmitButtonDisplayed());

D assertEquals(loginPage.isSubmitButtonDisplayed(), false);

💡 Hint

The method returns true if the button is visible.

Since isSubmitButtonDisplayed() returns true when the button is visible, assertTrue verifies this condition correctly. Other assertions either check for false or null, which are incorrect here.

❓ locator

advanced

Which locator follows best practices for a Page Object element?

You want to locate a login input field in your Page Object. Which locator is best practice?

A By.cssSelector("input")

B By.xpath("//input[@type='text']")

C By.id("loginInput")

D By.className("input-field")

💡 Hint

Use the most specific and stable locator.

By.id("loginInput") is the most specific and stable locator. XPath and CSS selectors shown are too generic and may select multiple elements. Class name may not be unique.

🔧 Debug

advanced

Why does this Page Object method throw NoSuchElementException?

This method tries to click a button but throws NoSuchElementException. What is the likely cause?

Selenium Java

public void clickLogin() {
    driver.findElement(By.id("loginBtn")).click();
}

A The driver is not initialized properly.

B The method should use findElements instead of findElement.

C The click() method is deprecated and causes the exception.

D The element with id "loginBtn" is not present or not yet loaded on the page.

💡 Hint

NoSuchElementException means Selenium cannot find the element.

NoSuchElementException occurs when the element is not found in the current page DOM. This usually means the element is missing or the page is not fully loaded.

❓ framework

expert

What is the main benefit of using the Page Object Model in Selenium tests?

Choose the best explanation for why the Page Object Model (POM) is used in Selenium test automation.

A It automatically generates test data for form inputs.

B It separates test code from page-specific code, improving maintainability and readability.

C It speeds up test execution by running tests in parallel.

D It replaces the need for assertions in test scripts.

💡 Hint

Think about how POM organizes code.

POM organizes web page elements and actions into classes, separating them from test logic. This makes tests easier to maintain and read. It does not generate data, speed execution, or remove assertions.