Why data-driven tests increase coverage in Selenium Python - Test Execution Impact

Test Overview

This test runs a login form check with multiple sets of usernames and passwords. It verifies that the login result matches the expected outcome for each data set. This shows how data-driven tests increase coverage by testing many cases in one test.

Test Code - Selenium

Selenium Python

import unittest
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 TestLoginDataDriven(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.driver.get('https://example.com/login')

    def test_login_multiple_users(self):
        test_data = [
            {'username': 'user1', 'password': 'pass1', 'expected': 'Welcome user1!'},
            {'username': 'user2', 'password': 'wrongpass', 'expected': 'Invalid credentials'},
            {'username': 'user3', 'password': 'pass3', 'expected': 'Welcome user3!'}
        ]

        for data in test_data:
            username_input = WebDriverWait(self.driver, 10).until(
                EC.presence_of_element_located((By.ID, 'username'))
            )
            password_input = self.driver.find_element(By.ID, 'password')
            login_button = self.driver.find_element(By.ID, 'login-btn')

            username_input.clear()
            username_input.send_keys(data['username'])
            password_input.clear()
            password_input.send_keys(data['password'])
            login_button.click()

            message = WebDriverWait(self.driver, 10).until(
                EC.visibility_of_element_located((By.ID, 'message'))
            ).text

            self.assertEqual(message, data['expected'])

    def tearDown(self):
        self.driver.quit()

if __name__ == '__main__':
    unittest.main()

Execution Trace - 9 Steps

Step	Action	System State	Assertion	Result
1	Test starts and browser opens the login page	Browser shows login page with username, password fields and login button	—	PASS
2	Find username, password input fields and login button	Elements are present and interactable	—	PASS
3	Enter username 'user1' and password 'pass1', then click login	Login form filled and submitted	—	PASS
4	Wait for message element and check text	Message displayed: 'Welcome user1!'	Assert message equals 'Welcome user1!'	PASS
5	Repeat steps 2-4 for username 'user2' and password 'wrongpass'	Login form filled and submitted	—	PASS
6	Wait for message element and check text	Message displayed: 'Invalid credentials'	Assert message equals 'Invalid credentials'	PASS
7	Repeat steps 2-4 for username 'user3' and password 'pass3'	Login form filled and submitted	—	PASS
8	Wait for message element and check text	Message displayed: 'Welcome user3!'	Assert message equals 'Welcome user3!'	PASS
9	Test ends and browser closes	Browser closed	—	PASS

Failure Scenario

Failing Condition: If the message text does not match the expected text for any data set

Execution Trace Quiz - 3 Questions

What does the test verify for each set of username and password?

A The displayed message matches the expected result

B The page URL changes after login

C The login button becomes disabled

D The browser title changes

Key Result

Data-driven tests improve coverage by running the same test steps with different inputs and expected results, catching more cases efficiently.

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