This test opens Google, searches for 'Selenium testing', and checks the page title contains the search term.
Selenium Python
import unittest
from selenium import webdriver
from selenium.webdriver.common.by import By
class HomePage:
def __init__(self, driver):
self.driver = driver
self.search_box = (By.NAME, 'q')
self.search_button = (By.NAME, 'btnK')
def search(self, text):
self.driver.find_element(*self.search_box).send_keys(text)
self.driver.find_element(*self.search_button).click()
class TestGoogleSearch(unittest.TestCase):
def setUp(self):
self.driver = webdriver.Chrome()
self.home_page = HomePage(self.driver)
def test_search(self):
self.driver.get('https://www.google.com')
self.home_page.search('Selenium testing')
self.assertIn('Selenium testing', self.driver.title)
def tearDown(self):
self.driver.quit()
if __name__ == '__main__':
unittest.main()
OutputSuccess
Important Notes
Use clear and unique locators to avoid flaky tests.
Keep page object methods focused on one action for clarity.
Always quit the browser in tearDown to free resources.
Summary
Page objects separate page details from test logic.
Test classes use page objects to perform actions and checks.
This approach makes tests easier to read and maintain.
Practice
(1/5)
1. What is the main purpose of using a page object in Selenium test classes?
easy
A. To separate page details from test logic for easier maintenance
B. To write all test steps inside the test class directly
C. To avoid using locators in tests
D. To run tests faster by skipping page loading
Solution
Step 1: Understand page object role
Page objects hold locators and page actions, separating them from test logic.
Step 2: Recognize test class role
Test classes use page objects to perform actions and assertions, improving readability and maintenance.
Final Answer:
To separate page details from test logic for easier maintenance -> Option A
Quick Check:
Page objects separate page details = C [OK]
Hint: Page objects keep page info separate from tests [OK]
Common Mistakes:
Thinking tests should contain locators directly
Believing page objects speed up test execution
Confusing page objects with test runners
2. Which of the following is the correct way to define a page object class in Python using Selenium?
easy
A. class LoginPage:
def __init__(self):
self.username_input = driver.find_element(By.ID, 'username')
B. def LoginPage(driver):
username_input = driver.find_element(By.ID, 'username')
C. class LoginPage:
def __init__(self, driver):
self.driver = driver
self.username_input = driver.find_element(By.ID, 'username')
D. class LoginPage:
def __init__(self, driver):
self.username_input = driver.find_element('username')
Solution
Step 1: Check class and constructor syntax
class LoginPage:
def __init__(self, driver):
self.driver = driver
self.username_input = driver.find_element(By.ID, 'username') correctly defines a class with __init__ accepting driver and assigns driver to self.driver.
Step 2: Verify locator usage
class LoginPage:
def __init__(self, driver):
self.driver = driver
self.username_input = driver.find_element(By.ID, 'username') uses driver.find_element with By.ID and locator string, which is correct Selenium syntax.
Final Answer:
Correct page object class with driver parameter and locator using By.ID -> Option C
Quick Check:
Class with __init__(driver) and By.ID locator = A [OK]
Hint: Page object classes need __init__(self, driver) and proper locators [OK]
Common Mistakes:
Missing driver parameter in __init__
Using driver.find_element without By selector
Defining page object as a function instead of class
3. Given the following test class using a page object, what will be printed if the username input is found and the page title is 'Login Page'?
A. LoginPage is instantiated without driver argument
B. send_keys method is called incorrectly
C. By.ID locator is invalid
D. test_enter_username method missing self parameter
Solution
Step 1: Check LoginPage instantiation
LoginPage requires driver argument in __init__, but called without arguments in test_enter_username.
Step 2: Verify other code parts
send_keys usage and By.ID locator are correct; test_enter_username has self parameter as method of class.
Final Answer:
LoginPage is instantiated without driver argument -> Option A
Quick Check:
Missing driver argument in LoginPage() call = B [OK]
Hint: Check constructor arguments when creating page object instances [OK]
Common Mistakes:
Forgetting to pass driver to page object constructor
Assuming send_keys needs different syntax
Confusing locator syntax errors
5. You want to write a test class that uses a page object to check if a login button is visible and clickable. Which approach correctly combines page object and test class methods?
hard
A. Test class calls page object method that returns the button WebElement but does not check visibility
B. Test class directly uses driver.find_element to check button visibility, ignoring page object
C. Page object only stores locators; test class performs all actions and assertions
D. Page object has method is_login_button_clickable() returning True/False; test class asserts this method's result
Solution
Step 1: Understand page object responsibility
Page objects should provide methods that check element states like visibility and clickability.
Step 2: Understand test class responsibility
Test class uses page object methods to assert expected conditions, keeping test logic separate from page details.
Final Answer:
Page object has method is_login_button_clickable() returning True/False; test class asserts this method's result -> Option D
Quick Check:
Page object checks state, test asserts result = D [OK]
Hint: Page object checks element state; test asserts result [OK]
Common Mistakes:
Mixing locator logic inside test class
Not returning boolean from page object methods
Ignoring visibility checks in tests
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.