Parameterized tests in Selenium Python - Framework Patterns

Framework Mode - Parameterized tests

Folder Structure

test_project/
├── tests/
│   ├── test_login.py
│   ├── test_search.py
│   └── test_checkout.py
├── pages/
│   ├── login_page.py
│   ├── search_page.py
│   └── checkout_page.py
├── utils/
│   ├── driver_factory.py
│   ├── test_data.py
│   └── helpers.py
├── config/
│   ├── config.yaml
│   └── credentials.yaml
├── conftest.py
└── pytest.ini

Test Framework Layers

• Driver Layer: Manages browser setup and teardown (e.g., driver_factory.py).
• Page Objects: Encapsulate page elements and actions (e.g., login_page.py).
• Tests: Test scripts using parameterized inputs (e.g., test_login.py with @pytest.mark.parametrize).
• Utilities: Helper functions and test data management (e.g., test_data.py for parameter sets).
• Configuration: Environment settings, credentials, and browser options (e.g., config.yaml).

Configuration Patterns

• Environment Config: Use config/config.yaml to define URLs, browsers, and environment variables.
• Credentials: Store sensitive data in credentials.yaml and load securely in tests.
• Parameter Data: Keep test input data in utils/test_data.py or external files (CSV/JSON) for easy updates.
• pytest.ini: Configure pytest options and markers for parameterized tests.
• Fixtures: Use conftest.py to provide reusable setup and parameter injection.

Test Reporting and CI/CD Integration

• Use pytest built-in reports with --junitxml=report.xml for CI tools.
• Integrate with CI/CD pipelines (GitHub Actions, Jenkins) to run parameterized tests on multiple environments.
• Use plugins like pytest-html for readable HTML reports showing each parameter set result.
• Configure test retries and failure screenshots for flaky tests.

Best Practices for Parameterized Tests

1. Keep test data separate: Store parameters outside test code for easy maintenance.
2. Use descriptive parameter names: Helps understand test cases in reports.
3. Limit parameter combinations: Avoid too many combinations to keep tests fast and focused.
4. Use fixtures for setup: Inject parameters cleanly and reuse setup code.
5. Validate all parameter cases: Ensure assertions cover all input variations.

Self Check

Where would you add a new set of login credentials to test multiple user types in this framework structure?

Key Result

Organize parameterized tests by separating test data, using fixtures, and structuring code into clear layers for maintainability and clarity.

Practice

1. What is the main benefit of using @pytest.mark.parametrize in Selenium Python tests?

easy

A. It allows running the same test with multiple sets of data easily.

B. It speeds up the browser loading time.

C. It automatically finds locators on the page.

D. It generates test reports without extra code.

Solution

1. Step 1: Understand the purpose of parameterized tests

   Parameterized tests run the same test logic multiple times with different input data sets.

2. Step 2: Identify what @pytest.mark.parametrize does

   This decorator allows easy setup of multiple data inputs for one test function, reducing repeated code.

3. Final Answer:

   It allows running the same test with multiple sets of data easily. -> Option A

4. Quick Check:

   Parameterized tests = multiple data sets [OK]

Hint: Think: same test, many inputs, less code [OK]

Common Mistakes:

• Confusing parameterization with browser speed optimization
• Thinking it auto-finds locators
• Assuming it auto-generates reports

2. Which of the following is the correct syntax to parameterize a test function with two parameters username and password using pytest?

easy

A. @pytest.mark.param('username', 'password', [('user1', 'pass1'), ('user2', 'pass2')])

B. @pytest.parametrize(['username', 'password'], [('user1', 'pass1'), ('user2', 'pass2')])

C. @pytest.mark.parametrize(('username', 'password'), ['user1', 'pass1', 'user2', 'pass2'])

D. @pytest.mark.parametrize('username, password', [('user1', 'pass1'), ('user2', 'pass2')])

Solution

1. Step 1: Recall pytest parameterize syntax

   The correct syntax uses @pytest.mark.parametrize with a string of comma-separated parameter names and a list of tuples for values.

2. Step 2: Compare options

   @pytest.mark.parametrize('username, password', [('user1', 'pass1'), ('user2', 'pass2')]) matches the correct syntax exactly. Others have wrong decorator names or wrong argument formats.

3. Final Answer:

   @pytest.mark.parametrize('username, password', [('user1', 'pass1'), ('user2', 'pass2')]) -> Option D

4. Quick Check:

   Correct decorator and tuple list = @pytest.mark.parametrize('username, password', [('user1', 'pass1'), ('user2', 'pass2')]) [OK]

Hint: Remember: mark.parametrize with string params and list of tuples [OK]

Common Mistakes:

• Misspelling 'parametrize' as 'parametrize' or 'param'
• Using list instead of tuple for parameter values
• Passing parameters as list instead of string

3. What will be the output when running this parameterized test snippet?

import pytest

@pytest.mark.parametrize('num, expected', [(1, 2), (2, 3), (3, 4)])
def test_increment(num, expected):
    assert num + 1 == expected

medium

A. Syntax error due to wrong decorator usage.

B. All tests fail due to assertion errors.

C. All tests pass successfully.

D. Only the first test passes, others fail.

Solution

1. Step 1: Analyze the test logic and parameters

   Each tuple provides num and expected. The test asserts num + 1 == expected. For (1,2), 1+1=2; for (2,3), 2+1=3; for (3,4), 3+1=4.

2. Step 2: Check if assertions hold for all cases

   All assertions are true, so all tests pass.

3. Final Answer:

   All tests pass successfully. -> Option C

4. Quick Check:

   num + 1 equals expected for all [OK]

Hint: Check each input-output pair matches assertion [OK]

Common Mistakes:

• Assuming some tests fail without checking values
• Confusing parameter order
• Thinking decorator syntax is wrong

4. Identify the error in this parameterized test code:

import pytest

@pytest.mark.parametrize('input, expected')
def test_double(input, expected):
    assert input * 2 == expected

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

medium

A. Wrong assertion operator used.

B. Missing data list for parameterize decorator on test_double.

C. Parameters names should be a list, not a string.

D. Test function name is invalid.

Solution

1. Step 1: Check the decorator usage on test_double

   The decorator @pytest.mark.parametrize('input, expected') is missing the second argument: the list of data tuples.

2. Step 2: Verify other parts

   Assertion and function name are correct. Parameter names as string is valid syntax.

3. Final Answer:

   Missing data list for parameterize decorator on test_double. -> Option B

4. Quick Check:

   Decorator needs data list argument [OK]

Hint: Always provide data list with parametrize decorator [OK]

Common Mistakes:

• Forgetting the data list argument
• Using list instead of string for parameter names (which is allowed but less common)
• Misreading assertion syntax

5. You want to test a login form with multiple username and password pairs using Selenium and pytest parameterization. Which approach correctly combines parameterized tests with Selenium WebDriver to test login functionality?

hard

A. Use @pytest.mark.parametrize to pass username and password, then inside the test open the browser, fill fields, submit, and assert login success.

B. Write separate test functions for each username and password pair without parameterization.

C. Use parameterization only for URLs, not for form inputs like username and password.

D. Use @pytest.mark.parametrize but do not open the browser inside the test function.

Solution

1. Step 1: Understand parameterized test purpose in Selenium context

   Parameterized tests allow running the same test logic with different input data, such as username and password pairs.

2. Step 2: Combine parameterization with Selenium actions

   Inside the test function, open the browser, fill the login form with parameters, submit, and check results. This is the correct approach.

3. Final Answer:

   Use @pytest.mark.parametrize to pass username and password, then inside the test open the browser, fill fields, submit, and assert login success. -> Option A

4. Quick Check:

   Parameterize inputs + Selenium actions inside test [OK]

Hint: Parameterize inputs, then automate browser steps inside test [OK]

Common Mistakes:

• Writing separate tests instead of parameterizing
• Not opening browser inside test function
• Limiting parameterization to URLs only