Why POM creates maintainable test code in Selenium Java - Quick Recap

Recall & Review

beginner

What does POM stand for in Selenium testing?

POM stands for Page Object Model. It is a design pattern that helps organize test code by creating separate classes for each web page.

beginner

How does POM improve test code maintainability?

POM improves maintainability by separating page structure and test logic. Changes in the UI require updates only in page classes, not in test scripts.

beginner

Why is it easier to update locators in POM?

Because all locators are stored in one place (the page class), updating a locator after UI changes is quick and does not affect test logic.

intermediate

What role do methods in page classes play in POM?

Methods in page classes represent user actions on the page, like clicking buttons or entering text. This hides complex code from tests, making tests simpler.

intermediate

How does POM help when multiple tests use the same page?

POM allows reuse of page classes across many tests, reducing duplicate code and making tests easier to write and maintain.

What is the main benefit of using POM in test automation?

A It separates page structure from test logic for easier maintenance

B It makes tests run faster

C It removes the need for locators

D It automatically generates test data

POM separates page details from test scripts, so UI changes only require updates in page classes, not all tests.

Where are locators stored in POM?

A In the page object class representing the page

B Inside the test scripts

C In a separate configuration file

D In the browser console

Locators are stored in the page class, centralizing UI element references for easy updates.

How does POM affect test code duplication?

A Has no effect

B Increases duplication

C Eliminates duplication by reusing page classes

D Duplicates locators only

POM promotes reuse of page classes, reducing repeated code in tests.

What do methods in a page class usually represent?

A Test assertions

B User actions on the page

C Database queries

D Test data generation

Methods in page classes model user actions like clicks or typing.

If the UI changes, what part of the test code usually needs updating in POM?

A Test reports

B All test scripts

C Test data files

D Page object classes only

Only page classes need updates because they hold locators and UI logic.

Explain how the Page Object Model (POM) helps keep test code maintainable.

Think about how changes in the website affect your test code.

Describe the role of methods inside a page class in POM and why they matter for maintainability.

Consider how you interact with a web page in your tests.

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