Why POM creates maintainable test code in Selenium Java - Framework Benefits

Framework Mode - Why POM creates maintainable test code

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   ├── LoginPage.java
                │   ├── HomePage.java
                │   └── DashboardPage.java
                ├── tests/
                │   ├── LoginTest.java
                │   └── DashboardTest.java
                ├── utils/
                │   ├── WebDriverFactory.java
                │   └── ConfigReader.java
                └── base/
                    └── BaseTest.java

Test Framework Layers

• Driver Layer: Manages browser setup and teardown (e.g., WebDriverFactory.java).
• Page Objects: Classes representing web pages with locators and methods (e.g., LoginPage.java). Encapsulates UI details.
• Tests: Test classes that use page objects to perform actions and assertions (e.g., LoginTest.java).
• Utilities: Helper classes for configuration, waits, logging (e.g., ConfigReader.java).
• Base Classes: Common setup and teardown logic shared by tests (e.g., BaseTest.java).

Configuration Patterns

Use property files or YAML to store environment URLs, browser types, and credentials.

Example: config.properties

base.url=https://example.com
browser=chrome
username=testuser
password=secret

Load config in ConfigReader.java and pass values to tests and page objects.

Use system properties or Maven profiles to switch environments and browsers without code changes.

Test Reporting and CI/CD Integration

• Use TestNG or JUnit reports for test results.
• Integrate with Allure or ExtentReports for detailed HTML reports with screenshots.
• Configure CI/CD pipelines (Jenkins, GitHub Actions) to run tests on code commits.
• Fail builds on test failures to ensure quality.

Framework Design Principles

• Separation of Concerns: Page Objects separate UI details from test logic, making tests easier to read and maintain.
• Reusability: Common page methods can be reused across multiple tests, reducing duplication.
• Encapsulation: Page Objects hide locators and interaction details, so changes in UI affect only page classes.
• Readability: Tests read like user actions, improving clarity for non-technical stakeholders.
• Scalability: Adding new pages or tests is straightforward without changing existing code.

Self Check

Where in this folder structure would you add a new page object for the "Profile" page?

Answer: Add ProfilePage.java inside the src/test/java/com/example/pages/ folder.

Key Result

Page Object Model creates maintainable test code by separating UI details from test logic, enabling easy updates and reuse.

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