Why POM organizes test code in Selenium Python - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Selenium WebDriver module.

Selenium Python

from selenium import [1]

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

Aseleniumbase

Bwebdriver_manager

Cwebdriver_remote

Dwebdriver

Attempts:

3 left

💡 Hint

Common Mistakes

Importing webdriver_manager instead of webdriver

Using wrong module names

The Selenium WebDriver module is imported using webdriver. This allows controlling the browser.

2fill in blank

medium

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

Selenium Python

class LoginPage:
    def __init__(self, driver):
        self.driver = [1]

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

Abrowser

Bsession

Cdriver

Dpage

Attempts:

3 left

💡 Hint

Common Mistakes

Using undefined variable names

Assigning wrong parameter

The constructor stores the WebDriver instance in self.driver to use it in page methods.

3fill in blank

hard

Fix the error in the method that clicks the login button using a locator.

Selenium Python

def click_login(self):
    login_button = self.driver.find_element_by_[1]("loginBtn")
    login_button.click()

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

Aid

Bname

Cclass_name

Dxpath

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong locator methods like name or class_name

Typos in method names

The method find_element_by_id locates elements by their id attribute, which is correct here.

4fill in blank

hard

Fill both blanks to create a method that enters username and password.

Selenium Python

def login(self, username, password):
    self.driver.find_element_by_[1]("username").send_keys(username)
    self.driver.find_element_by_[2]("password").send_keys(password)

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

Aid

Bname

Cclass_name

Dtag_name

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing locator types for username and password

Using class_name or tag_name incorrectly

Using find_element_by_id for both username and password fields is common when their HTML elements have id attributes.

5fill in blank

hard

Fill the two blanks to write a test that uses the LoginPage object to perform login and verify success.

Selenium Python

def test_login():
    driver = webdriver.Chrome()
    login_page = LoginPage(driver)
    driver.get("http://example.com/login")
    login_page.login([1], [2])
    login_page.click_login()
    assert "Dashboard" in driver.title
    driver.quit()

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

A"user1"

B"pass123"

C"admin"

D"password"

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect argument types

Not quitting the driver after test

The test calls login with username "user1" and password "pass123". The assertion checks if "Dashboard" is in the page title after login.

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