Element locators in page class in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ locator

intermediate

Identify the best locator for a login button

You have a login button with HTML: <button id='loginBtn' class='btn primary'>Login</button>. Which locator is the most reliable and efficient to use in a Selenium page class?

A driver.find_element(By.XPATH, "//button[text()='Login']")

B driver.find_element(By.CLASS_NAME, 'btn')

C driver.find_element(By.ID, 'loginBtn')

D driver.find_element(By.CSS_SELECTOR, 'button.primary')

💡 Hint

Think about uniqueness and speed of locating elements.

Using By.ID is the fastest and most reliable because IDs are unique on the page. Class names or CSS selectors might match multiple elements, and XPath is slower.

❓ assertion

intermediate

Choose the correct assertion for verifying page title

You want to check if the page title is exactly 'Welcome Page' after login. Which assertion is correct in a Python unittest test case?

A self.assertEqual(driver.title, 'Welcome Page')

B self.assertTrue(driver.title == 'Welcome Page')

C self.assertIn('Welcome', driver.title)

D self.assertIs(driver.title, 'Welcome Page')

💡 Hint

Check which assertion method compares values for equality properly.

assertEqual checks if two values are exactly equal. assertTrue works but is less clear. assertIn only checks substring presence. assertIs checks object identity, not value equality.

❓ Predict Output

advanced

What is the output of this Selenium locator code?

Given the following page class snippet, what will print(len(page.buttons)) output if the page has 3 buttons with class 'btn'?

Selenium Python

from selenium.webdriver.common.by import By

class Page:
    def __init__(self, driver):
        self.driver = driver
    
    @property
    def buttons(self):
        return self.driver.find_elements(By.CLASS_NAME, 'btn')

# Assume driver is a Selenium WebDriver instance with 3 buttons having class 'btn'
page = Page(driver)
print(len(page.buttons))

A Raises NoSuchElementException

B 1

C 0

D 3

💡 Hint

Remember that find_elements returns a list of matching elements.

find_elements returns a list of all matching elements. Since there are 3 buttons with class 'btn', the length is 3. It does not raise an exception if no elements are found; it returns an empty list.

🔧 Debug

advanced

Find the error in this page class locator

What is wrong with this locator in the page class?

Selenium Python

from selenium.webdriver.common.by import By

class LoginPage:
    def __init__(self, driver):
        self.driver = driver
    
    username_input = (By.ID, 'username')
    
    def enter_username(self, name):
        self.driver.find_element(*self.username_input).send_keys(name)

A No error, code works fine

B find_element expects two arguments, not a tuple

C send_keys is called on a tuple, not a WebElement

D username_input should be a method, not a tuple

💡 Hint

Check how find_element is called with locators.

find_element requires two arguments: locator strategy and locator value. Passing a tuple as a single argument causes a TypeError. The correct call is find_element(*self.username_input) to unpack the tuple.

❓ framework

expert

Which test framework feature best supports page class locators?

In a Selenium test suite using Python, which feature of the pytest framework helps manage page class locators efficiently and promotes clean test code?

A Using pytest fixtures to initialize page objects

B Using pytest.mark.parametrize to test multiple locators

C Using pytest.raises to catch locator errors

D Using pytest.skip to ignore locator tests

💡 Hint

Think about how to reuse page objects across tests.

Pytest fixtures allow setup code to create and provide page objects with locators to tests, promoting reuse and clean code. Parametrize is for data-driven tests, raises is for exception testing, skip is for ignoring tests.

Practice

1. What is the main purpose of using element locators in a page class in Selenium Python?

easy

A. To find web elements clearly and reuse them easily

B. To write complex test logic inside the page class

C. To store test data separately from the test scripts

D. To execute browser commands directly

Solution

1. Step 1: Understand the role of element locators

   Element locators help identify web elements on a page so tests can interact with them.

2. Step 2: Recognize the benefit of using a page class

   Storing locators in a page class allows easy reuse and keeps code clean.

3. Final Answer:

   To find web elements clearly and reuse them easily -> Option A

4. Quick Check:

   Element locators = reuse and clarity [OK]

Hint: Locators in page class = find elements + reuse [OK]

Common Mistakes:

• Confusing locators with test data storage
• Thinking page class runs browser commands
• Assuming locators hold test logic

2. Which of the following is the correct way to define a locator for a button with id 'submit' in a Selenium page class?

easy

A. submit_button = By('id', 'submit')

B. submit_button = By.ID('submit')

C. submit_button = ('id', submit)

D. submit_button = (By.ID, 'submit')

Solution

1. Step 1: Recall the correct locator tuple format

   Locators are tuples with By strategy and string value, e.g., (By.ID, 'value').

2. Step 2: Check each option's syntax

   submit_button = (By.ID, 'submit') uses (By.ID, 'submit'), which is correct. Others use wrong syntax or missing quotes.

3. Final Answer:

   submit_button = (By.ID, 'submit') -> Option D

4. Quick Check:

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

Hint: Locator = (By.<STRATEGY>, 'value') tuple [OK]

Common Mistakes:

• Using By.ID('submit') instead of tuple
• Missing quotes around 'submit'
• Using wrong tuple structure

3. Given the locator login_button = (By.CSS_SELECTOR, 'button.login') in a page class, what will driver.find_element(*login_button) do?

medium

A. Cause a syntax error because of unpacking

B. Find the first button element with class 'login' on the page

C. Find all button elements with class 'login' on the page

D. Find an element by tag name 'button.login'

Solution

1. Step 1: Understand the locator tuple and unpacking

   The locator is a tuple (By.CSS_SELECTOR, 'button.login'). Using * unpacks it into two arguments.

2. Step 2: Know what find_element does

   find_element returns the first matching element, not all elements.

3. Final Answer:

   Find the first button element with class 'login' on the page -> Option B

4. Quick Check:

   find_element + CSS selector = first match [OK]

Hint: find_element finds first match, unpack locator tuple [OK]

Common Mistakes:

• Confusing find_element with find_elements
• Thinking unpacking causes syntax error
• Misunderstanding CSS selector as tag name

4. You have this locator in your page class: search_box = (By.NAME, 'q'). Your test code uses driver.find_element(search_box) and fails. What is the error and how to fix it?

medium

A. Error: Missing unpacking operator '*'. Fix: Use driver.find_element(*search_box)

B. Error: Wrong locator type. Fix: Change By.NAME to By.ID

C. Error: Locator value is incorrect. Fix: Change 'q' to 'search'

D. Error: find_element cannot use tuples. Fix: Use string locator only

Solution

1. Step 1: Identify the cause of failure

   driver.find_element expects two arguments, but passing a tuple without unpacking sends one argument.

2. Step 2: Apply the correct fix

   Use the unpacking operator * to pass locator as separate arguments: driver.find_element(*search_box).

3. Final Answer:

   Error: Missing unpacking operator '*'. Fix: Use driver.find_element(*search_box) -> Option A

4. Quick Check:

   Unpack locator tuple with * [OK]

Hint: Always unpack locator tuple with * in find_element [OK]

Common Mistakes:

• Not using * causes TypeError
• Changing locator type unnecessarily
• Assuming locator value is wrong

5. You want to create a page class locator for a link with text 'Home' that may appear as either an <a> tag or a <button> tag. Which locator is best to find it reliably?

hard

A. home_link = (By.LINK_TEXT, 'Home')

B. home_link = (By.CSS_SELECTOR, 'a.home, button.home')

C. home_link = (By.XPATH, "//a[text()='Home'] | //button[text()='Home']")

D. home_link = (By.ID, 'home')

Solution

1. Step 1: Understand the locator requirements

   The element can be either an <a> or <button> with text 'Home', so locator must cover both tags.

2. Step 2: Evaluate locator options

   home_link = (By.XPATH, "//a[text()='Home'] | //button[text()='Home']") uses XPath with OR (|) to match either tag by exact text, which is reliable. home_link = (By.LINK_TEXT, 'Home') only works for <a> tags. home_link = (By.CSS_SELECTOR, 'a.home, button.home') uses classes which may not exist. home_link = (By.ID, 'home') uses ID which is not given.

3. Final Answer:

   home_link = (By.XPATH, "//a[text()='Home'] | //button[text()='Home']") -> Option C

4. Quick Check:

   XPath OR matches multiple tags [OK]

Hint: Use XPath OR (|) to match multiple tag types [OK]

Common Mistakes:

• Using LINK_TEXT misses button tags
• Using CSS selectors without classes
• Assuming ID exists without confirmation