PageFactory initialization in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this PageFactory initialization code?

Consider the following Selenium Java code snippet initializing a Page Object. What will be the output when the test runs and tries to click the button?

Selenium Java

public class LoginPage {
    @FindBy(id = "submitBtn")
    private WebElement submitButton;

    public LoginPage(WebDriver driver) {
        PageFactory.initElements(driver, this);
    }

    public void clickSubmit() {
        submitButton.click();
        System.out.println("Clicked Submit");
    }
}

// In test method:
WebDriver driver = new ChromeDriver();
driver.get("http://example.com/login");
LoginPage page = new LoginPage(driver);
page.clickSubmit();

A Clicked Submit

B NullPointerException at submitButton.click()

C NoSuchElementException at PageFactory.initElements

D WebDriverException due to driver not initialized

💡 Hint

Think about what PageFactory.initElements does and when the element is located.

PageFactory.initElements initializes the WebElement fields so that when clickSubmit() is called, submitButton is a proxy that locates the element at click time. Since the driver is valid and the element exists, the click succeeds and prints 'Clicked Submit'.

❓ assertion

intermediate

Which assertion correctly verifies PageFactory initialized element is displayed?

Given a Page Object with a WebElement 'loginButton' initialized by PageFactory, which assertion correctly checks if the button is visible on the page?

Selenium Java

public class HomePage {
    @FindBy(id = "loginBtn")
    private WebElement loginButton;

    public HomePage(WebDriver driver) {
        PageFactory.initElements(driver, this);
    }

    public boolean isLoginButtonVisible() {
        return loginButton.isDisplayed();
    }
}

// Test method snippet:
HomePage home = new HomePage(driver);
boolean visible = home.isLoginButtonVisible();

A assertNull(visible);

B assertTrue(visible);

C assertEquals(visible, false);

D assertFalse(loginButton == null);

💡 Hint

Check which assertion confirms a boolean is true.

Since isLoginButtonVisible() returns a boolean indicating visibility, assertTrue(visible) correctly asserts the button is visible. Other options either check wrong conditions or wrong types.

🔧 Debug

advanced

Why does this PageFactory initialization cause NullPointerException?

Examine the code below. Why does calling click() on the 'searchButton' cause a NullPointerException?

Selenium Java

public class SearchPage {
    @FindBy(name = "search")
    private WebElement searchButton;

    public SearchPage() {
        PageFactory.initElements(this, this);
    }

    public void clickSearch() {
        searchButton.click();
    }
}

// Test snippet:
SearchPage page = new SearchPage();
page.clickSearch();

A PageFactory requires @FindBy on public fields only

B searchButton locator is invalid causing element not found

C searchButton is private and cannot be accessed

D PageFactory.initElements called with wrong arguments; driver missing

💡 Hint

Check the parameters passed to PageFactory.initElements.

PageFactory.initElements requires a WebDriver instance as the first argument to locate elements. Passing 'this' instead of a driver causes the WebElement fields to remain null, leading to NullPointerException on click.

🧠 Conceptual

advanced

What is the main advantage of using PageFactory.initElements in Selenium?

Why do testers prefer using PageFactory.initElements to initialize WebElements in Page Object classes?

A It converts WebElements to strings for easier debugging

B It automatically retries finding elements on failure without extra code

C It creates lazy proxies for WebElements, locating them only when used

D It immediately finds all elements on page load to speed up tests

💡 Hint

Think about when the element is actually located in the DOM.

PageFactory.initElements creates proxy objects for WebElements that locate the elements only when a method like click() or getText() is called. This lazy loading improves test performance and stability.

❓ framework

expert

Which PageFactory initialization pattern best supports parallel test execution?

In a Selenium test framework designed for parallel execution, which PageFactory initialization approach is best to avoid WebDriver conflicts?

A Initialize PageFactory inside each test method using the test's own WebDriver instance

B Create PageFactory objects before WebDriver initialization to reuse them

C Initialize PageFactory with a null WebDriver and set elements later

D Use a static WebDriver shared across all tests and initialize PageFactory once globally

💡 Hint

Consider thread safety and WebDriver instance scope in parallel tests.

For parallel tests, each test must have its own WebDriver instance. Initializing PageFactory inside each test method with that test's driver ensures no conflicts or shared state, supporting thread safety.