Why data-driven tests increase coverage in Selenium Python

Introduction

Data-driven tests let us check many input cases easily. This helps find more problems and makes tests stronger.

When you want to test a form with many different input values.

When you need to check how a website behaves with various user data.

When you want to run the same test steps but with different data sets.

When you want to avoid writing many similar tests manually.

When you want to improve test coverage without extra effort.

Syntax

Selenium Python

for data in test_data:
    perform_test(data)

Use a loop to run the same test with different data.

Test data can come from lists, files, or databases.

Examples

This example runs a login test for three users.

Selenium Python

test_data = ["user1", "user2", "user3"]
for user in test_data:
    print(f"Testing login for {user}")

This example tests login with username and password pairs.

Selenium Python

test_data = [("user1", "pass1"), ("user2", "pass2")]
for username, password in test_data:
    print(f"Testing with {username} and {password}")

Sample Program

This test tries logging in with different usernames and passwords. It checks if login succeeds or fails as expected. This way, many cases are covered with one test function.

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By
import time

def test_login(username, password):
    driver = webdriver.Chrome()
    driver.get("https://example.com/login")
    driver.find_element(By.ID, "username").send_keys(username)
    driver.find_element(By.ID, "password").send_keys(password)
    driver.find_element(By.ID, "login-button").click()
    time.sleep(1)  # wait for page to load
    success = "Welcome" in driver.page_source
    driver.quit()
    assert success, f"Login failed for {username}"

# Data sets to test
credentials = [
    ("validUser", "validPass"),
    ("invalidUser", "validPass"),
    ("validUser", "wrongPass")
]

for user, pwd in credentials:
    try:
        test_login(user, pwd)
        print(f"Test passed for {user}")
    except AssertionError as e:
        print(e)

Important Notes

Data-driven tests reduce repeated code and save time.

Make sure test data covers both normal and edge cases.

Keep test data organized and easy to update.

Summary

Data-driven tests run the same steps with many inputs.

This increases test coverage and finds more bugs.

It makes tests easier to maintain and expand.

Practice

1. Why do data-driven tests increase test coverage in Selenium Python?

easy

A. Because they skip validation steps

B. Because they reduce the number of test cases to one

C. Because they only test the UI layout

D. Because they run the same test steps with many different inputs

Solution

1. Step 1: Understand data-driven testing concept

   Data-driven tests repeat the same test steps but use different input data sets.

2. Step 2: Connect data variation to coverage

   Using many inputs helps test more scenarios, increasing coverage and finding more bugs.

3. Final Answer:

   Because they run the same test steps with many different inputs -> Option D

4. Quick Check:

   Data-driven tests = many inputs = more coverage [OK]

Hint: More inputs mean more scenarios tested [OK]

Common Mistakes:

• Thinking data-driven tests reduce test cases
• Confusing UI layout testing with data-driven testing
• Believing data-driven tests skip validations

2. Which of the following is the correct way to pass multiple data sets to a Selenium Python test using pytest parameterization?

easy

A. @pytest.parametrization('input', [1, 2, 3])

B. @pytest.parametrize('input', (1, 2, 3))

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

D. @pytest.mark.parametrized('input', [1, 2, 3])

Solution

1. Step 1: Recall pytest parameterization syntax

   The correct decorator is @pytest.mark.parametrize with 'param' and list of values.

2. Step 2: Check each option syntax

   Only @pytest.mark.parametrize('input', [1, 2, 3]) uses correct spelling and syntax: @pytest.mark.parametrize('input', [1, 2, 3]).

3. Final Answer:

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

4. Quick Check:

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

Hint: Remember exact decorator spelling: parametrize with 'z' [OK]

Common Mistakes:

• Misspelling 'parametrize' as 'parametrize' or 'parametrized'
• Using parentheses instead of brackets for data list
• Confusing 'param' and 'parametrize'

3. Given this pytest data-driven test snippet, what will be the output if the test fails for input 3?

import pytest

@pytest.mark.parametrize('num', [1, 2, 3])
def test_is_even(num):
    assert num % 2 == 0

medium

A. Test fails only for input 3

B. Test fails for inputs 1 and 3

C. Test passes for all inputs

D. Test fails for input 2 only

Solution

1. Step 1: Understand the test logic

   The test asserts num % 2 == 0, meaning num must be even.

2. Step 2: Check each input

   Input 1: 1 % 2 = 1 (fail), Input 2: 2 % 2 = 0 (pass), Input 3: 3 % 2 = 1 (fail).

3. Final Answer:

   Test fails for inputs 1 and 3 -> Option B

4. Quick Check:

   Odd numbers fail assertion [OK]

Hint: Even numbers pass; odd numbers fail [OK]

Common Mistakes:

• Assuming only input 3 fails
• Thinking all inputs pass
• Confusing modulo operation results

4. Identify the error in this data-driven Selenium Python test code snippet:

@pytest.mark.parametrize('username, password', [('user1', 'pass1'), ('user2', 'pass2')])
def test_login(username, password):
    driver.get('http://example.com/login')
    driver.find_element(By.ID, 'username').send_keys(username)
    driver.find_element(By.ID, 'password').send_keys(password)
    driver.find_element(By.ID, 'submit').click()
    assert driver.find_element(By.ID, 'welcome').is_displayed()

medium

A. Missing import for By locator

B. Incorrect parameter names in parametrize decorator

C. Using send_keys on a button element

D. No assertion to check login success

Solution

1. Step 1: Review code for missing imports

   The code uses By.ID but does not show import of By from selenium.webdriver.common.by.

2. Step 2: Check other code parts

   Parameter names match, send_keys used correctly on input fields, assertion checks welcome element display.

3. Final Answer:

   Missing import for By locator -> Option A

4. Quick Check:

   Using By requires importing it [OK]

Hint: Check all used classes are imported [OK]

Common Mistakes:

• Assuming parameter names are wrong
• Thinking send_keys is used on button
• Missing assertion is incorrect here

5. How does using data-driven tests in Selenium Python help maintain and expand test suites efficiently?

hard

A. By allowing reuse of test logic with new data sets without rewriting tests

B. By requiring a new test function for every input variation

C. By limiting tests to only one data set to reduce complexity

D. By removing the need for assertions in tests

Solution

1. Step 1: Understand test maintenance challenges

   Writing separate tests for each input is time-consuming and hard to maintain.

2. Step 2: Explain data-driven test advantage

   Data-driven tests reuse the same test code with different inputs, making it easy to add or change data without rewriting code.

3. Final Answer:

   By allowing reuse of test logic with new data sets without rewriting tests -> Option A

4. Quick Check:

   Reuse test logic + new data = easier maintenance [OK]

Hint: Reuse code, just add data sets [OK]

Common Mistakes:

• Thinking each input needs a new test function
• Believing data-driven tests reduce assertions
• Assuming data-driven tests limit data sets