Why POM creates maintainable test code in Selenium Java - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a Page Object class for the login page.

Selenium Java

public class LoginPage {
    private WebDriver driver;

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

Drag options to blanks, or click blank then click option'

Adriver

Bpage

CwebDriver

Dbrowser

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different parameter name causes the driver field to remain null.

The constructor parameter should be named driver to assign it correctly to the class field.

2fill in blank

medium

Complete the code to locate the username input field using a best practice locator.

Selenium Java

private By usernameField = By.[1]("username");

Drag options to blanks, or click blank then click option'

AclassName

Bid

CcssSelector

Dxpath

Attempts:

3 left

💡 Hint

Common Mistakes

Using xpath unnecessarily makes tests slower and harder to maintain.

Using By.id is the best practice locator when the element has a unique id attribute.

3fill in blank

hard

Fix the error in the method that enters the username text.

Selenium Java

public void enterUsername(String username) {
    driver.findElement(usernameField).[1](username);
}

Drag options to blanks, or click blank then click option'

Aclick

BgetText

CsendKeys

Dclear

Attempts:

3 left

💡 Hint

Common Mistakes

Using click instead of sendKeys does not enter text.

The sendKeys method types text into input fields.

4fill in blank

hard

Fill both blanks to create a method that clicks the login button and waits for the home page.

Selenium Java

public void clickLogin() {
    driver.findElement([1]).click();
    new WebDriverWait(driver, Duration.ofSeconds(10))
        .until(ExpectedConditions.[2](By.id("homePage")));
}

Drag options to blanks, or click blank then click option'

AloginButton

BvisibilityOfElementLocated

Cclickable

DsubmitButton

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong locator names or waiting conditions causes test failures.

The method clicks the login button and waits until the home page element is visible.

5fill in blank

hard

Fill in the blank to define a Page Object method that returns the page title after login.

Selenium Java

public String getPageTitle() {
    return driver.[1]();
}

Drag options to blanks, or click blank then click option'

AswitchTo

BgetWindowHandle

CpageTitle

DgetTitle

Attempts:

3 left

💡 Hint

Common Mistakes

Using getWindowHandle returns a window handle, not the title.

switchTo() is for changing driver context, not retrieving the title.

The getTitle() method on WebDriver returns the title of the current page. No locator or switching is needed.

Practice

1. What is the main reason the Page Object Model (POM) helps create maintainable test code?

easy

A. It runs tests faster by using parallel execution.

B. It separates page structure from test logic, making updates easier.

C. It requires less code to write tests.

D. It automatically fixes broken tests.

Solution

1. Step 1: Understand POM structure

   POM organizes code by separating page details (locators, actions) from test steps.

2. Step 2: Identify maintenance benefit

   This separation means if the page changes, only the page object needs updating, not all tests.

3. Final Answer:

   It separates page structure from test logic, making updates easier. -> Option B

4. Quick Check:

   Separation of concerns = easier maintenance [OK]

Hint: Remember: POM separates page and test code for easy updates [OK]

Common Mistakes:

• Thinking POM speeds up test execution
• Believing POM reduces code amount drastically
• Assuming POM auto-fixes test failures

2. Which of the following is the correct way to define a WebElement in a Page Object class using Selenium Java?

easy

A. WebElement button = driver.findElement(By.name);

B. WebElement button = driver.findElement("submit");

C. WebElement button = driver.findElement(By.id("submit"));

D. WebElement button = driver.findElement(By.id);

Solution

1. Step 1: Recall correct syntax for locating elements

   In Selenium Java, findElement requires a By locator like By.id("value").

2. Step 2: Check each option

   WebElement button = driver.findElement(By.id("submit")); uses By.id with a string, which is correct. Others miss the locator type or string.

3. Final Answer:

   WebElement button = driver.findElement(By.id("submit")); -> Option C

4. Quick Check:

   Use By.id("value") for locating elements [OK]

Hint: Use By.id("value") or By.name("value") with findElement [OK]

Common Mistakes:

• Omitting the locator type (By.id, By.name)
• Passing locator type without string
• Using findElement with just a string

3. Given the following Page Object method, what will be the output when calling loginPage.getTitle() if the page title is "Welcome Page"?

public class LoginPage {
  WebDriver driver;
  public LoginPage(WebDriver driver) {
    this.driver = driver;
  }
  public String getTitle() {
    return driver.getTitle();
  }
}

medium

A. "Welcome Page"

B. "Login Page"

C. null

D. Throws NullPointerException

Solution

1. Step 1: Understand getTitle() method

   The method returns the title of the current page from the WebDriver.

2. Step 2: Given page title is "Welcome Page"

   Calling getTitle() returns the actual page title string, which is "Welcome Page".

3. Final Answer:

   "Welcome Page" -> Option A

4. Quick Check:

   driver.getTitle() returns current page title [OK]

Hint: driver.getTitle() returns the current page title string [OK]

Common Mistakes:

• Confusing method return with page object name
• Assuming method returns null or exception without driver
• Thinking getTitle() returns page URL

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

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

medium

A. loginBtn should be declared as WebElement[] instead of WebElement.

B. click() method cannot be called on WebElement.

C. driver.findElement should be replaced with driver.findElements.

D. By.id is missing the locator string; fix by adding the id value.

Solution

1. Step 1: Check findElement syntax

   By.id requires a string argument like By.id("loginBtn"), but here it is missing.

2. Step 2: Fix the locator

   Add the id string inside By.id, e.g., By.id("loginBtn") to correctly locate the element.

3. Final Answer:

   By.id is missing the locator string; fix by adding the id value. -> Option D

4. Quick Check:

   By.id("value") needs a string argument [OK]

Hint: Always provide locator string inside By.id("value") [OK]

Common Mistakes:

• Omitting the locator string in By.id
• Using findElements when only one element needed
• Thinking click() is invalid on WebElement

5. How does using the Page Object Model (POM) save time when the website under test changes its layout or element locators?

hard

A. Only the Page Object classes need updates, not all test scripts.

B. Tests automatically adapt without any code changes.

C. POM uses AI to detect and fix locator changes.

D. Test scripts are deleted and rewritten faster.

Solution

1. Step 1: Understand POM's separation of concerns

   POM keeps locators and page actions inside Page Object classes, separate from test logic.

2. Step 2: Effect of website changes

   If locators or layout change, only the Page Object classes need updating, so tests remain unchanged.

3. Final Answer:

   Only the Page Object classes need updates, not all test scripts. -> Option A

4. Quick Check:

   Update page objects, keep tests stable [OK]

Hint: Update page objects only when UI changes, not all tests [OK]

Common Mistakes:

• Believing tests auto-update without code changes
• Thinking POM uses AI or automation to fix locators
• Assuming tests must be rewritten after UI changes