Parameterize with test data in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of parameterized test with multiple data sets

Given the following pytest test function using parameterization, what will be the output when running the test?

Selenium Python

import pytest

@pytest.mark.parametrize('input,expected', [(2, 4), (3, 9), (4, 16)])
def test_square(input, expected):
    assert input * input == expected

# What is the test result summary?

A 3 tests passed

B 2 tests passed, 1 failed

C All tests failed

D 1 test passed, 2 failed

💡 Hint

Check if the assertion matches the expected square values.

Each input is squared and compared to the expected value. All pairs are correct, so all tests pass.

❓ assertion

intermediate

Correct assertion for parameterized Selenium test

You have a Selenium test that checks page titles for multiple URLs using parameterization. Which assertion correctly verifies the page title matches the expected title?

Selenium Python

from selenium import webdriver
import pytest

@pytest.mark.parametrize('url,expected_title', [
    ('https://example.com', 'Example Domain'),
    ('https://www.python.org', 'Welcome to Python.org')
])
def test_page_title(url, expected_title):
    driver = webdriver.Chrome()
    driver.get(url)
    # Which assertion is correct here?
    # assert ???
    driver.quit()

A assert expected_title in driver.page_source

B assert driver.title != expected_title

C assert driver.title == expected_title

D assert driver.current_url == expected_title

💡 Hint

Page title is accessed by driver.title property.

The correct way to check the page title is to compare driver.title with the expected title string.

🔧 Debug

advanced

Identify the error in parameterized Selenium test code

What error will occur when running this parameterized Selenium test code?

Selenium Python

import pytest
from selenium import webdriver

@pytest.mark.parametrize('url', ['https://example.com', 'https://python.org'])
def test_open_page(url):
    driver = webdriver.Chrome
    driver.get(url)
    assert 'Example' in driver.title
    driver.quit()

A AttributeError: 'function' object has no attribute 'get'

B No error, test passes

C NameError: name 'driver' is not defined

D TypeError: 'WebDriver' object is not callable

💡 Hint

Check how the webdriver.Chrome is used.

webdriver.Chrome is a class and must be called with parentheses to create an instance. Missing parentheses means driver is assigned the class itself, not an instance, so driver.get() causes AttributeError.

❓ framework

advanced

Best practice for parameterizing Selenium tests with pytest fixtures

Which option shows the best way to combine pytest fixtures and parameterization for Selenium tests to reuse the browser instance efficiently?

A Use @pytest.mark.parametrize on test function and create a new driver inside each test

B Use @pytest.fixture with parameters and create driver inside fixture for each test

C Create driver globally outside tests and parametrize tests without fixtures

D Use a session-scoped fixture to create driver once and parametrize test with @pytest.mark.parametrize

💡 Hint

Think about reusing browser instance to speed up tests.

Using a session-scoped fixture creates the driver once per test session, improving efficiency. Parameterizing tests separately allows running tests with different data using the same driver instance.

🧠 Conceptual

expert

Why parameterize tests in Selenium automation?

What is the main advantage of parameterizing Selenium tests with multiple data sets?

A It makes tests run faster by parallelizing browser instances automatically

B It reduces code duplication and allows running the same test logic with different inputs automatically

C It ensures tests only run once with fixed data to avoid flaky results

D It removes the need for assertions by validating all inputs implicitly

💡 Hint

Think about how parameterization affects test coverage and code reuse.

Parameterization helps run the same test code with different inputs, reducing duplication and increasing coverage without writing multiple test functions.