Why POM organizes test code in Selenium Python - Automation Benefits in Action

Verify login functionality using Page Object Model

Preconditions (2)

Step 1: Open the login page URL

Step 2: Enter '[e-mail]' in the email input field

Step 3: Enter 'Test@1234' in the password input field

Step 4: Click the login button

Step 5: Verify that the user is redirected to the dashboard page

✅ Expected Result: User successfully logs in and dashboard page is displayed

Automation Requirements - Selenium with Python

Assertions Needed:

Verify current URL is dashboard URL after login

Verify login button is clickable before clicking

Verify email and password fields accept input

Best Practices:

Use Page Object Model to separate page locators and actions

Use explicit waits to wait for elements

Keep test logic separate from page interaction code

Automated Solution

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

class LoginPage:
    def __init__(self, driver):
        self.driver = driver
        self.email_input = (By.ID, 'email')
        self.password_input = (By.ID, 'password')
        self.login_button = (By.ID, 'loginBtn')

    def enter_email(self, email):
        email_field = WebDriverWait(self.driver, 10).until(
            EC.visibility_of_element_located(self.email_input))
        email_field.clear()
        email_field.send_keys(email)

    def enter_password(self, password):
        password_field = WebDriverWait(self.driver, 10).until(
            EC.visibility_of_element_located(self.password_input))
        password_field.clear()
        password_field.send_keys(password)

    def click_login(self):
        login_btn = WebDriverWait(self.driver, 10).until(
            EC.element_to_be_clickable(self.login_button))
        login_btn.click()


def test_login():
    driver = webdriver.Chrome()
    driver.get('https://example.com/login')

    login_page = LoginPage(driver)
    login_page.enter_email('[e-mail]')
    login_page.enter_password('Test@1234')
    login_page.click_login()

    WebDriverWait(driver, 10).until(
        EC.url_contains('/dashboard'))

    assert '/dashboard' in driver.current_url, 'Dashboard URL not loaded after login'

    driver.quit()

This code uses the Page Object Model (POM) to organize test code.

The LoginPage class holds all locators and actions for the login page. This keeps selectors and interaction logic in one place.

The test function test_login uses this class to perform steps clearly and simply.

Explicit waits ensure elements are ready before interacting, avoiding flaky tests.

Assertions check that the login succeeded by verifying the URL.

This separation makes the test easier to read, maintain, and update if the page changes.

Common Mistakes - 3 Pitfalls

Putting locators and test steps together in the test function

Not using explicit waits before interacting with elements

Hardcoding URLs and credentials inside test functions

Bonus Challenge

Now add data-driven testing with 3 different sets of login credentials

Show Hint

Practice

1. What is the main reason to use the Page Object Model (POM) in Selenium test automation?

easy

A. To separate page details from test logic for cleaner code

B. To write all test steps in one big script

C. To avoid using locators in tests

D. To run tests faster by skipping waits

Solution

1. Step 1: Understand POM purpose

   POM separates the page structure (locators and actions) from the test logic, making code cleaner.

2. Step 2: Compare options

   Options A, B, and D do not describe POM's main goal. Only To separate page details from test logic for cleaner code correctly states the separation of concerns.

3. Final Answer:

   To separate page details from test logic for cleaner code -> Option A

4. Quick Check:

   POM purpose = Separation of concerns [OK]

Hint: Remember: POM splits page info and test steps [OK]

Common Mistakes:

• Thinking POM speeds up test execution
• Believing POM removes locators completely
• Confusing POM with test data management

2. Which of the following is the correct way to define a locator in a POM class using Selenium with Python?

easy

A. self.login_button = driver.find_element_by_id('login')

B. login_button = ('id', 'login')

C. login_button = (By.ID, 'login')

D. login_button = driver.find_element(By.ID, 'login')

Solution

1. Step 1: Recall POM locator best practice

   In POM, locators are stored as tuples like (By.ID, 'value') without calling find_element immediately.

2. Step 2: Analyze options

   login_button = (By.ID, 'login') correctly defines a locator tuple. Options A and C call find_element directly, which is not best practice. login_button = ('id', 'login') uses a string 'id' instead of By.ID.

3. Final Answer:

   login_button = (By.ID, 'login') -> Option C

4. Quick Check:

   Locator tuple = (By.ID, 'login') [OK]

Hint: Locators in POM are tuples with By.<type> [OK]

Common Mistakes:

• Calling find_element when defining locators
• Using strings instead of By constants
• Storing locators as WebElements instead of tuples

3. Given this POM method in Python:

def click_login(self):
    self.driver.find_element(*self.login_button).click()

What happens if the locator self.login_button is incorrect?

medium

A. The test will pass but skip the click

B. The test will raise a TimeoutException

C. The test will ignore the error and continue

D. The test will fail with NoSuchElementException

Solution

1. Step 1: Understand Selenium behavior on wrong locator

   If the locator is wrong, Selenium cannot find the element and raises NoSuchElementException immediately.

2. Step 2: Check other options

   Options A and C are incorrect because Selenium does not silently skip or ignore missing elements. The test will raise a TimeoutException is wrong because TimeoutException occurs with explicit waits, not direct find_element calls.

3. Final Answer:

   The test will fail with NoSuchElementException -> Option D

4. Quick Check:

   Wrong locator = NoSuchElementException [OK]

Hint: Wrong locator causes NoSuchElementException [OK]

Common Mistakes:

• Confusing NoSuchElementException with TimeoutException
• Thinking Selenium skips missing elements
• Assuming test passes without element

4. You have this POM method:

def enter_username(self, username):
    self.driver.find_element(*self.username_field).send_keys(username)

But tests fail with NoSuchElementException. What is the likely cause?

medium

A. The username argument is None

B. The locator self.username_field is incorrect

C. send_keys method is misspelled

D. The driver is not initialized

Solution

1. Step 1: Analyze the error message

   NoSuchElementException means Selenium cannot find the element, so self.username_field locator is likely incorrect.

2. Step 2: Check other options

   The username argument is None is wrong because that would error after finding the element. send_keys method is misspelled is unlikely as send_keys is standard. The driver is not initialized would cause different errors.

3. Final Answer:

   The locator self.username_field is incorrect -> Option B

4. Quick Check:

   NoSuchElementException = locator wrong [OK]

Hint: NoSuchElementException means locator wrong [OK]

Common Mistakes:

• Blaming input argument for locator error
• Ignoring locator definition
• Assuming driver is always initialized

5. How does using POM help a team when the web page changes its button ID from 'submit' to 'send'?

hard

A. Only the locator in the POM class needs updating, tests remain unchanged

B. All test scripts must be rewritten to use the new ID

C. Tests will fail until the whole framework is rebuilt

D. The change has no effect because POM uses dynamic locators automatically

Solution

1. Step 1: Understand POM's separation advantage

   POM stores locators in one place. Changing a locator means updating only that place.

2. Step 2: Evaluate options

   Only the locator in the POM class needs updating, tests remain unchanged correctly states only the locator in POM needs update. All test scripts must be rewritten to use the new ID is wrong because tests don't need rewriting. Tests will fail until the whole framework is rebuilt exaggerates failure. The change has no effect because POM uses dynamic locators automatically is false; POM does not auto-update locators.

3. Final Answer:

   Only the locator in the POM class needs updating, tests remain unchanged -> Option A

4. Quick Check:

   POM isolates locator changes [OK]

Hint: Update locator once in POM, not all tests [OK]

Common Mistakes:

• Thinking all tests must change
• Believing POM auto-fixes locators
• Assuming framework rebuild is needed