Why advanced patterns handle real-world complexity in PyTest - Automation Benefits in Action

Automate login and profile update with complex user flows

Preconditions (2)

Step 1: Enter 'testuser' in the username field

Step 2: Enter 'Test@1234' in the password field

Step 3: Click the login button

Step 4: Wait until the dashboard page loads

Step 5: Navigate to the profile settings page

Step 6: Update the user's display name to 'Test User Updated'

Step 7: Save the changes

Step 8: Verify that a success message 'Profile updated successfully' is displayed

Step 9: Log out from the application

Step 10: Verify that the login page is displayed again

✅ Expected Result: User logs in successfully, updates profile display name, sees success message, and logs out returning to login page

Automation Requirements - pytest with Selenium WebDriver

Assertions Needed:

Verify dashboard page URL after login

Verify profile update success message is visible

Verify login page URL after logout

Best Practices:

Use Page Object Model to separate page interactions

Use explicit waits to handle dynamic page loading

Use pytest fixtures for setup and teardown

Use clear and reusable locators

Use assertions with meaningful messages

Automated Solution

PyTest

import 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

class LoginPage:
    def __init__(self, driver):
        self.driver = driver
        self.username_input = (By.ID, 'username')
        self.password_input = (By.ID, 'password')
        self.login_button = (By.ID, 'loginBtn')

    def login(self, username, password):
        self.driver.find_element(*self.username_input).clear()
        self.driver.find_element(*self.username_input).send_keys(username)
        self.driver.find_element(*self.password_input).clear()
        self.driver.find_element(*self.password_input).send_keys(password)
        self.driver.find_element(*self.login_button).click()

class DashboardPage:
    def __init__(self, driver):
        self.driver = driver
        self.profile_link = (By.ID, 'profileLink')

    def wait_for_dashboard(self):
        WebDriverWait(self.driver, 10).until(
            EC.url_contains('/dashboard')
        )

    def go_to_profile(self):
        self.driver.find_element(*self.profile_link).click()

class ProfilePage:
    def __init__(self, driver):
        self.driver = driver
        self.display_name_input = (By.ID, 'displayName')
        self.save_button = (By.ID, 'saveProfile')
        self.success_message = (By.ID, 'successMsg')

    def update_display_name(self, new_name):
        self.driver.find_element(*self.display_name_input).clear()
        self.driver.find_element(*self.display_name_input).send_keys(new_name)
        self.driver.find_element(*self.save_button).click()

    def wait_for_success_message(self):
        WebDriverWait(self.driver, 10).until(
            EC.visibility_of_element_located(self.success_message)
        )

    def get_success_message_text(self):
        return self.driver.find_element(*self.success_message).text

class BasePage:
    def __init__(self, driver):
        self.driver = driver
        self.logout_button = (By.ID, 'logoutBtn')

    def logout(self):
        self.driver.find_element(*self.logout_button).click()

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

@pytest.mark.usefixtures('driver')
def test_login_update_profile_logout(driver):
    driver.get('https://example.com/login')

    login_page = LoginPage(driver)
    login_page.login('testuser', 'Test@1234')

    dashboard_page = DashboardPage(driver)
    dashboard_page.wait_for_dashboard()
    assert '/dashboard' in driver.current_url, 'Dashboard URL not loaded after login'

    dashboard_page.go_to_profile()

    profile_page = ProfilePage(driver)
    profile_page.update_display_name('Test User Updated')
    profile_page.wait_for_success_message()
    success_text = profile_page.get_success_message_text()
    assert success_text == 'Profile updated successfully', 'Success message not shown or incorrect'

    base_page = BasePage(driver)
    base_page.logout()

    WebDriverWait(driver, 10).until(
        EC.url_contains('/login')
    )
    assert '/login' in driver.current_url, 'Login page not shown after logout'

This test script uses the Page Object Model to organize code for each page: LoginPage, DashboardPage, ProfilePage, and BasePage for logout. This keeps locators and actions in one place, making maintenance easier.

We use explicit waits (WebDriverWait) to wait for pages to load or messages to appear, which handles real-world delays and dynamic content.

The pytest fixture driver sets up and tears down the browser cleanly.

Assertions check the URL after login and logout, and verify the success message text after profile update, ensuring the test validates expected outcomes clearly.

This approach handles real-world complexity by separating concerns, waiting properly, and making tests readable and maintainable.

Common Mistakes - 3 Pitfalls

Using hardcoded sleep (time.sleep) instead of explicit waits

Mixing locators and test logic in the test function

Not verifying important outcomes like URL changes or success messages

Bonus Challenge

Now add data-driven testing with 3 different user credentials and display names

Show Hint

Practice

1. What is the main benefit of using fixtures in pytest for complex tests?

easy

A. They automatically handle setup and cleanup for tests.

B. They make tests run faster by skipping assertions.

C. They replace the need for writing test functions.

D. They generate random test data automatically.

Solution

1. Step 1: Understand the role of fixtures

   Fixtures in pytest are designed to prepare the environment before a test runs and clean up after it finishes.

2. Step 2: Identify the benefit in complex tests

   By managing setup and cleanup automatically, fixtures reduce repeated code and make tests clearer and easier to maintain.

3. Final Answer:

   They automatically handle setup and cleanup for tests. -> Option A

4. Quick Check:

   Fixtures = setup and cleanup automation [OK]

Hint: Fixtures manage setup/cleanup so tests stay clean [OK]

Common Mistakes:

• Thinking fixtures speed up tests by skipping assertions
• Believing fixtures replace test functions
• Assuming fixtures generate random data automatically

2. Which of the following is the correct syntax to parametrize a test function in pytest?

easy

A. @pytest.parametrize('input,expected', [(1,2), (3,4)])

B. @pytest.mark.parametrize('input,expected', [(1,2), (3,4)])

C. @pytest.parametrize('input,expected', [1,2,3,4])

D. @pytest.parametrize('input,expected', {1:2, 3:4})

Solution

1. Step 1: Recall pytest parametrize decorator syntax

   The correct decorator is @pytest.mark.parametrize with the parameters as a string and a list of tuples.

2. Step 2: Check each option

   @pytest.mark.parametrize('input,expected', [(1,2), (3,4)]) uses the correct decorator with a list of tuples. Incorrect options omit '.mark.', use a flat list instead of tuples, or use a dictionary instead of a list of tuples.

3. Final Answer:

   @pytest.mark.parametrize('input,expected', [(1,2), (3,4)]) -> Option B

4. Quick Check:

   Correct decorator = @pytest.mark.parametrize [OK]

Hint: Remember: it's @pytest.mark.parametrize with list of tuples [OK]

Common Mistakes:

• Using @pytest.parametrize instead of @pytest.mark.parametrize
• Using a flat list like [1,2,3,4] instead of list of tuples
• Passing a dictionary instead of a list of tuples

3. Given the following pytest code, what will be the output when running the test?

import pytest

@pytest.mark.parametrize('x,y', [(1,2), (3,4)])
def test_sum(x, y):
    assert x + y == 3

medium

A. SyntaxError due to parametrize decorator

B. Both tests pass

C. Both tests fail

D. First test passes, second test fails

Solution

1. Step 1: Analyze the parametrized inputs and assertion

   The test runs twice: first with x=1, y=2; second with x=3, y=4. The assertion checks if x + y == 3.

2. Step 2: Evaluate each test case

   For (1,2), 1+2=3, assertion passes. For (3,4), 3+4=7, assertion fails.

3. Final Answer:

   First test passes, second test fails -> Option D

4. Quick Check:

   1+2=3 pass, 3+4=7 fail [OK]

Hint: Check each input pair against assertion separately [OK]

Common Mistakes:

• Assuming both tests pass without checking values
• Confusing syntax error with correct decorator usage
• Ignoring that second input fails assertion

4. Identify the error in this pytest fixture code snippet:

import pytest

@pytest.fixture
def setup_data():
    data = {'key': 'value'}
    return data

def test_data(setup_data):
    assert setup_data['key'] == 'value'

medium

A. Fixture function missing yield statement

B. Fixture is not used as a parameter in test function

C. No error; code runs correctly

D. Fixture function name conflicts with test function

Solution

1. Step 1: Review fixture definition and usage

   The fixture 'setup_data' returns a dictionary. The test function accepts it as a parameter and asserts a key's value.

2. Step 2: Check for common fixture errors

   The fixture is correctly defined with @pytest.fixture, used as a parameter, and returns data properly. No yield is needed unless cleanup is required.

3. Final Answer:

   No error; code runs correctly -> Option C

4. Quick Check:

   Fixture usage correct = no error [OK]

Hint: Fixtures can return data without yield if no cleanup needed [OK]

Common Mistakes:

• Thinking yield is mandatory in fixtures
• Forgetting to pass fixture as test parameter
• Assuming fixture name conflicts with test function

5. You want to test a function with many input combinations efficiently. Which advanced pytest pattern helps you avoid writing many similar test functions?

hard

A. Parametrizing tests with @pytest.mark.parametrize

B. Using print statements to check outputs manually

C. Writing separate test functions for each input

D. Using multiple assert statements in one test

Solution

1. Step 1: Understand the problem of many input combinations

   Writing many test functions for each input is repetitive and hard to maintain.

2. Step 2: Identify the pytest feature for efficient input testing

   @pytest.mark.parametrize allows running the same test function multiple times with different inputs automatically.

3. Step 3: Compare options

   Parametrizing tests with @pytest.mark.parametrize uses parametrization, which is the recommended advanced pattern. Using multiple assert statements, print statements to check manually, or writing separate test functions are inefficient or manual approaches.

4. Final Answer:

   Parametrizing tests with @pytest.mark.parametrize -> Option A

5. Quick Check:

   Parametrize = efficient multiple inputs [OK]

Hint: Use @pytest.mark.parametrize to run tests with many inputs [OK]

Common Mistakes:

• Writing many separate test functions instead of parametrizing
• Using print instead of assertions
• Trying to test many inputs in one test without parametrization