Page Object Model concept in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Page Object Model

What is the main purpose of using the Page Object Model (POM) in software testing?

A To automatically generate test data for input fields

B To speed up test execution by running tests in parallel

C To separate test code from page-specific code to improve maintainability

D To replace manual testing with exploratory testing

💡 Hint

Think about how POM helps when the web page changes.

The Page Object Model helps keep the code organized by separating the page structure and actions from the test logic. This makes tests easier to maintain when the UI changes.

❓ Predict Output

intermediate

Output of POM method call

Given the following simplified Page Object Model class and test code, what will be printed?

Testing Fundamentals

class LoginPage:
    def __init__(self):
        self.page_title = "Login Page"
    def get_title(self):
        return self.page_title

page = LoginPage()
print(page.get_title())

A Login Page

B page_title

C None

D Error: get_title is not defined

💡 Hint

Look at what get_title() returns.

The method get_title() returns the string stored in the page_title attribute, which is "Login Page".

❓ locator

advanced

Best locator strategy in POM

Which locator strategy is considered best practice for identifying a button in a Page Object Model class for stable and maintainable tests?

A Using class name that is shared by many buttons like .btn

B Using XPath with absolute path like /html/body/div[2]/button[1]

C Using text content matching like button[text()='Submit']

D Using CSS selector with a unique ID attribute like #submitBtn

💡 Hint

Unique and stable attributes are best for locators.

Using a unique ID attribute with a CSS selector is the most stable and maintainable locator strategy. Absolute XPath is fragile, text matching can break if text changes, and class names may not be unique.

❓ assertion

advanced

Correct assertion for page title

In a test using POM, which assertion correctly verifies that the page title is exactly 'Dashboard'?

Testing Fundamentals

page = DashboardPage()
actual_title = page.get_title()

A assert actual_title == 'Dashboard'

B assert actual_title > 'Dashboard'

C assert actual_title != 'Dashboard'

D assert 'Dashboard' in actual_title

💡 Hint

Check for exact match, not partial or inequality.

To verify the page title exactly matches 'Dashboard', use equality assertion. Option A checks only if 'Dashboard' is part of the title, which is less strict.

❓ framework

expert

POM integration with test framework

In a test automation framework using POM, which practice best supports test scalability and reusability?

A Instantiate page objects inside each test method separately

B Create a base test class that initializes page objects once per test class

C Write all test steps directly inside the test methods without page objects

D Use global variables for page objects shared across all tests

💡 Hint

Think about avoiding repeated code and easy maintenance.

Creating a base test class that initializes page objects once per test class promotes reusability and reduces duplication. Instantiating inside each test method repeats code, and global variables can cause test interference.

Practice

1. What is the main purpose of the Page Object Model in software testing?

easy

A. To combine multiple test cases into one large script

B. To write all test steps inside the test script without abstraction

C. To separate page structure from test logic for easier maintenance

D. To avoid using classes and methods in test automation

Solution

1. Step 1: Understand the role of Page Object Model

   The Page Object Model (POM) is designed to separate the page details like locators and actions from the test scripts.

2. Step 2: Identify the benefit of separation

   This separation makes tests easier to read, write, and maintain because changes in the UI only affect the page objects, not the test logic.

3. Final Answer:

   To separate page structure from test logic for easier maintenance -> Option C

4. Quick Check:

   Separation of concerns = A [OK]

Hint: POM separates page details from tests for easy updates [OK]

Common Mistakes:

• Thinking POM combines all tests into one script
• Believing POM avoids using classes and methods
• Confusing POM with writing test steps directly in scripts

2. Which of the following is the correct way to define a page object class for a login page in Python?

easy

A. class LoginPage:
def __init__(self, driver):
self.driver = driver

B. def LoginPage(driver):
self.driver = driver

C. class LoginPage:
driver = driver

D. LoginPage = function(driver) { this.driver = driver; }

Solution

1. Step 1: Check Python class syntax for page object

   In Python, a page object is a class with an __init__ method that accepts the driver and assigns it to self.driver.

2. Step 2: Identify correct syntax

   class LoginPage: def __init__(self, driver): self.driver = driver correctly defines a class with __init__ and assigns driver properly. Options A, B, and D have syntax errors or misuse of class variables. LoginPage = function(driver) { this.driver = driver; } is JavaScript syntax, not Python.

3. Final Answer:

   class LoginPage: def __init__(self, driver): self.driver = driver -> Option A

4. Quick Check:

   Python class with __init__ = C [OK]

Hint: Python page objects use class with __init__ for driver [OK]

Common Mistakes:

• Using function instead of class for page object
• Assigning driver outside __init__ method
• Mixing JavaScript syntax in Python code

3. Given this Python page object method, what will login_page.get_title() return if the page title is "Welcome"?

class LoginPage:
    def __init__(self, driver):
        self.driver = driver
    def get_title(self):
        return self.driver.title

medium

A. "Welcome"

B. self.driver

C. None

D. Error: method missing return

Solution

1. Step 1: Understand the get_title method

   The method returns self.driver.title, which is the page title property from the driver object.

2. Step 2: Determine the returned value

   If the page title is "Welcome", calling get_title() returns the string "Welcome".

3. Final Answer:

   "Welcome" -> Option A

4. Quick Check:

   Method returns driver.title = "Welcome" [OK]

Hint: Method returns driver.title property value [OK]

Common Mistakes:

• Confusing method return with driver object itself
• Assuming method returns None without explicit return
• Thinking method causes error due to missing return

4. Identify the error in this page object method and select the fix:

class LoginPage:
    def __init__(self, driver):
        self.driver = driver
    def click_login(self):
        self.driver.find_element_by_id('loginBtn').click()

medium

A. Change method name to clickLogin

B. Use correct locator method: replace find_element_by_id with find_element(By.ID, 'loginBtn')

C. Remove self.driver assignment in __init__

D. Add return statement after click()

Solution

1. Step 1: Check Selenium locator method usage

   In recent Selenium versions, find_element_by_id is deprecated. The correct usage is find_element(By.ID, 'loginBtn') with proper import.

2. Step 2: Identify the fix

   Use correct locator method: replace find_element_by_id with find_element(By.ID, 'loginBtn') correctly updates the locator method. Other options do not fix the locator error or are unrelated.

3. Final Answer:

   Use correct locator method: replace find_element_by_id with find_element(By.ID, 'loginBtn') -> Option B

4. Quick Check:

   Update deprecated locator method = D [OK]

Hint: Use updated Selenium locators with By.ID [OK]

Common Mistakes:

• Ignoring deprecated locator methods
• Adding unnecessary return statements
• Changing method names without reason

5. You want to create a page object for a search page that has a method to enter text and submit the search. Which design best follows the Page Object Model principles?

hard

A. class SearchPage:
def __init__(self):
self.driver = None
def search(self, text):
self.driver.find_element(By.ID, 'searchBox').send_keys(text)

B. class SearchPage:
def search(self, text):
input = driver.find_element(By.NAME, 'q')
input.send_keys(text)
input.submit()

C. def search(text):
driver.find_element(By.NAME, 'q').send_keys(text)
driver.find_element(By.NAME, 'q').submit()

D. class SearchPage:
def __init__(self, driver):
self.driver = driver
def search(self, text):
box = self.driver.find_element(By.NAME, 'q')
box.clear()
box.send_keys(text)
box.submit()

Solution

1. Step 1: Check for proper driver initialization

   class SearchPage: def __init__(self, driver): self.driver = driver def search(self, text): box = self.driver.find_element(By.NAME, 'q') box.clear() box.send_keys(text) box.submit() correctly initializes the driver in __init__, so the page object has access to it.

2. Step 2: Verify method encapsulates actions

   The search method finds the input box, clears it, sends keys, and submits, all encapsulated in one method, following POM principles.

3. Final Answer:

   class SearchPage: def __init__(self, driver): self.driver = driver def search(self, text): box = self.driver.find_element(By.NAME, 'q') box.clear() box.send_keys(text) box.submit() -> Option D

4. Quick Check:

   Driver init + encapsulated method = A [OK]

Hint: Initialize driver in __init__ and encapsulate actions in methods [OK]

Common Mistakes:

• Not initializing driver in constructor
• Using global driver without passing it
• Splitting one action into multiple unrelated methods