Why patterns improve test quality in PyTest - Automation Benefits in Action

Automate login functionality using Page Object pattern

Preconditions (2)

Step 1: Open the login page URL in a browser

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

Step 3: Enter 'Password123' 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 - pytest with Selenium WebDriver

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 interactions from test logic

Use explicit waits to wait for elements to be ready

Use clear and descriptive assertion messages

Automated Solution

PyTest

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
import pytest

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 load(self, url):
        self.driver.get(url)

    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()

@pytest.fixture
def driver():
    driver = webdriver.Chrome()
    yield driver
    driver.quit()


def test_login_success(driver):
    login_page = LoginPage(driver)
    login_page.load("https://example.com/login")
    login_page.enter_email("[e-mail]")
    login_page.enter_password("Password123")
    login_page.click_login()

    WebDriverWait(driver, 10).until(
        EC.url_contains("/dashboard")
    )
    assert "/dashboard" in driver.current_url, "User should be redirected to dashboard after login"

This test uses the Page Object Model (POM) pattern to improve test quality by separating page details from test logic. The LoginPage class encapsulates all interactions with the login page elements. This makes the test test_login_success easier to read and maintain.

Explicit waits ensure elements are ready before interacting, avoiding flaky tests. Assertions check that the user is redirected to the dashboard URL after login, confirming success.

Using pytest fixtures for the WebDriver setup and teardown keeps the test clean and reusable.

Common Mistakes - 3 Pitfalls

Hardcoding element locators inside the test function

Using implicit waits or no waits at all

Not verifying that elements are interactable before clicking

Bonus Challenge

Now add data-driven testing with 3 different sets of login credentials (valid and invalid)

Show Hint

Practice

1. Why do testing patterns improve the quality of pytest tests?

easy

A. They make tests clearer and easier to understand

B. They make tests run faster by skipping assertions

C. They allow tests to ignore errors safely

D. They reduce the number of tests needed

Solution

1. Step 1: Understand the role of patterns in clarity

   Patterns organize test code so it is easier to read and understand by others.

2. Step 2: Recognize how clarity improves quality

   Clear tests are easier to maintain and less likely to have hidden mistakes.

3. Final Answer:

   They make tests clearer and easier to understand -> Option A

4. Quick Check:

   Patterns improve clarity = B [OK]

Hint: Patterns improve clarity and maintenance [OK]

Common Mistakes:

• Thinking patterns make tests run faster
• Believing patterns allow ignoring errors
• Assuming patterns reduce test count

2. Which pytest code snippet follows a good pattern for reusing setup code?

easy

A. @pytest.fixture
def setup(): pass
def test_one(setup): assert True

B. def setup(): pass
def test_one(): setup(); assert True

C. def test_one(): setup(); assert True

D. def test_one(): assert True

Solution

1. Step 1: Identify pytest fixture usage

   Using @pytest.fixture allows sharing setup code cleanly across tests.

2. Step 2: Check test function uses fixture parameter

   Passing the fixture as a parameter ensures setup runs before the test.

3. Final Answer:

   @pytest.fixture\ndef setup(): pass\ndef test_one(setup): assert True -> Option A

4. Quick Check:

   Use fixtures for setup = A [OK]

Hint: Look for @pytest.fixture and parameter use [OK]

Common Mistakes:

• Calling setup manually inside test
• Defining setup without fixture decorator
• Not using fixtures for reusable setup

3. What will be the output when running this pytest test following a pattern for clear assertions?

def test_sum():
    result = sum([1, 2, 3])
    assert result == 6

medium

A. Test is skipped automatically

B. Test fails with AssertionError

C. SyntaxError due to missing colon

D. Test passes successfully

Solution

1. Step 1: Calculate the sum in the test

   sum([1, 2, 3]) equals 6, so result is 6.

2. Step 2: Check the assertion condition

   assert result == 6 is True, so no error is raised.

3. Final Answer:

   Test passes successfully -> Option D

4. Quick Check:

   sum([1,2,3]) == 6 passes = D [OK]

Hint: Calculate values, then check assertion truth [OK]

Common Mistakes:

• Assuming assertion fails without checking values
• Confusing syntax errors with logic errors
• Thinking tests skip without skip decorator

4. Identify the error in this pytest test that breaks a common pattern for test clarity:

def test_divide():
    result = 10 / 0
    assert result == 0

medium

A. Test function missing pytest decorator

B. Assertion compares wrong expected value

C. Division by zero causes runtime error

D. Result variable is not defined

Solution

1. Step 1: Analyze the division operation

   Dividing 10 by 0 causes a ZeroDivisionError at runtime.

2. Step 2: Understand impact on test execution

   The test will error out before reaching the assertion, breaking clarity and reliability.

3. Final Answer:

   Division by zero causes runtime error -> Option C

4. Quick Check:

   ZeroDivisionError breaks test = C [OK]

Hint: Check for runtime errors before assertions [OK]

Common Mistakes:

• Ignoring runtime errors in tests
• Assuming assertion runs despite error
• Thinking pytest decorator is required for functions

5. How does using pytest fixtures as a pattern improve test maintenance when multiple tests share setup code?

hard

A. Fixtures automatically fix test failures without changes

B. Fixtures centralize setup, reducing repeated code and easing updates

C. Fixtures run tests in parallel to speed execution

D. Fixtures hide test details to simplify reports

Solution

1. Step 1: Understand fixture role in setup sharing

   Fixtures provide a single place to write setup code used by many tests.

2. Step 2: Recognize maintenance benefits

   Changing setup in one fixture updates all tests, avoiding repeated code and errors.

3. Final Answer:

   Fixtures centralize setup, reducing repeated code and easing updates -> Option B

4. Quick Check:

   Fixtures reduce repetition = A [OK]

Hint: Fixtures share setup code for easy maintenance [OK]

Common Mistakes:

• Believing fixtures fix failures automatically
• Confusing fixtures with parallel test runners
• Thinking fixtures hide test details