Base page class pattern in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of BasePage method call

Given the following BasePage class snippet, what will be the output when getPageTitle() is called if the current page title is "Home - MyApp"?

Selenium Java

public class BasePage {
    protected WebDriver driver;

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

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

// Assume driver.getTitle() returns "Home - MyApp"

A "Home - MyApp"

B "MyApp - Home"

C null

D ""

💡 Hint

Think about what the getTitle() method of WebDriver returns.

The getPageTitle() method returns the title of the current page by calling driver.getTitle(), which returns the exact page title string.

❓ assertion

intermediate

Correct assertion for page title verification

Which assertion correctly verifies that the page title is exactly "Dashboard - MyApp" in a test using the BasePage class?

Selenium Java

BasePage basePage = new BasePage(driver);
String actualTitle = basePage.getPageTitle();

A assertTrue(actualTitle.contains("Dashboard"));

B assertFalse(actualTitle.isEmpty());

C assertNotNull(actualTitle);

D assertEquals("Dashboard - MyApp", actualTitle);

💡 Hint

Exact match is required for the title.

assertEquals compares the expected and actual strings exactly, which is needed to verify the full page title.

❓ locator

advanced

Best locator strategy in BasePage for a common header element

In the BasePage class, which locator is the best practice to find a header element with id "main-header"?

A By.cssSelector("header#main-header")

B By.xpath("//header[@id='main-header']")

C By.id("main-header")

D By.className("main-header")

💡 Hint

Id locators are fastest and most reliable if unique.

Using By.id("main-header") is the fastest and most reliable locator if the id is unique on the page.

🔧 Debug

advanced

Identify the error in BasePage constructor

What error will occur when creating a BasePage object with this constructor code snippet?

Selenium Java

public class BasePage {
    protected WebDriver driver;

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

A driver is not initialized; NullPointerException when used

B Compilation error: driver cannot be assigned to itself

C SyntaxError: missing parameter in constructor

D No error; code works fine

💡 Hint

Look at how driver is assigned in the constructor.

The constructor has no parameter, so 'driver' on right side is the field itself, so it remains null causing NullPointerException later.

❓ framework

expert

Best practice for extending BasePage in Page Object Model

In a Page Object Model using BasePage as a parent class, which approach correctly initializes the driver in a child page class named LoginPage?

Selenium Java

public class LoginPage extends BasePage {
    private By usernameField = By.id("username");

    public LoginPage(WebDriver driver) {
        // What should go here?
    }
}

A super();

B super(driver);

C this.driver = driver;

D driver = new WebDriver();

💡 Hint

Use the parent constructor to initialize inherited fields.

Calling super(driver) passes the driver to the BasePage constructor to initialize the protected driver field properly.