Test class using page objects in Selenium Python - Framework Patterns

Framework Mode - Test class using page objects

Folder Structure

project_root/
├── tests/
│   ├── test_login.py
│   └── test_search.py
├── pages/
│   ├── base_page.py
│   ├── login_page.py
│   └── search_page.py
├── utils/
│   ├── driver_factory.py
│   └── config_reader.py
├── resources/
│   └── test_data.json
├── conftest.py
└── pytest.ini
    

Test Framework Layers

• Driver Layer: Manages browser setup and teardown (e.g., driver_factory.py).
• Page Objects: Classes representing web pages with locators and actions (e.g., login_page.py).
• Test Classes: Test scripts using page objects to perform tests (e.g., test_login.py).
• Utilities: Helpers for config reading, waits, logging (e.g., config_reader.py).
• Test Data: External files holding test inputs (e.g., test_data.json).

Configuration Patterns

Use pytest.ini or conftest.py to manage configurations.

• Define environment variables or command line options for browser type (Chrome, Firefox).
• Store URLs, credentials in resources/test_data.json or environment variables.
• Use fixtures in conftest.py to initialize and quit WebDriver instances.

Test Reporting and CI/CD Integration

• Use pytest built-in reporting with options like --junitxml=report.xml for XML reports.
• Integrate with CI tools (GitHub Actions, Jenkins) to run tests on code push.
• Generate HTML reports using plugins like pytest-html for easy visualization.
• Configure test retries and screenshots on failure for better debugging.

Best Practices

• Page Object Model: Keep locators and page actions in page classes to separate test logic from UI details.
• Use Explicit Waits: Avoid fixed sleeps; wait for elements to be ready before interacting.
• Reusable Fixtures: Use pytest fixtures for setup/teardown to keep tests clean.
• Data-Driven Testing: Separate test data from code to run tests with multiple inputs easily.
• Clear Naming: Name page objects and test methods clearly to improve readability.

Self Check

Where would you add a new page object class for the "Profile" page in this framework structure?

Key Result

Use Page Object Model with clear folder layers and pytest fixtures for clean Selenium Python tests.

Practice

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

1. Step 1: Understand page object role

   Page objects hold locators and page actions, separating them from test logic.

2. Step 2: Recognize test class role

   Test classes use page objects to perform actions and assertions, improving readability and maintenance.

3. Final Answer:

   To separate page details from test logic for easier maintenance -> Option A

4. 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

1. 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.

2. 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.

3. Final Answer:

   Correct page object class with driver parameter and locator using By.ID -> Option C

4. 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'?

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

class TestLogin:
    def test_title(self, driver):
        page = LoginPage(driver)
        print(page.get_title())

# Assume driver.title = 'Login Page'

medium

A. None

B. Login Page

C. driver.title

D. Error: driver not defined

Solution

1. Step 1: Understand get_title method

   get_title returns driver.title, which is 'Login Page' as given.

2. Step 2: Check test_title method output

   test_title creates LoginPage instance and prints get_title result, so it prints 'Login Page'.

3. Final Answer:

   Login Page -> Option B

4. Quick Check:

   page.get_title() returns 'Login Page' [OK]

Hint: get_title returns driver.title, prints page title string [OK]

Common Mistakes:

• Confusing method return with attribute name
• Assuming print outputs None
• Thinking driver is undefined inside test method

4. Identify the error in this test class using a page object:

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

class TestLogin:
    def test_enter_username(self, driver):
        page = LoginPage()
        page.enter_username('user1')

medium

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

1. Step 1: Check LoginPage instantiation

   LoginPage requires driver argument in __init__, but called without arguments in test_enter_username.

2. 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.

3. Final Answer:

   LoginPage is instantiated without driver argument -> Option A

4. 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

1. Step 1: Understand page object responsibility

   Page objects should provide methods that check element states like visibility and clickability.

2. Step 2: Understand test class responsibility

   Test class uses page object methods to assert expected conditions, keeping test logic separate from page details.

3. Final Answer:

   Page object has method is_login_button_clickable() returning True/False; test class asserts this method's result -> Option D

4. 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