Why advanced patterns handle real-world complexity in PyTest - Test Execution Impact

Test Overview

This test checks a function that calculates discounts based on complex rules. It verifies that the function correctly applies multiple conditions, showing how advanced patterns help manage real-world complexity.

Test Code - pytest

PyTest

import pytest

def calculate_discount(price, customer_type, is_holiday):
    if price <= 0:
        return 0
    if customer_type == 'VIP' and is_holiday:
        return price * 0.3
    elif customer_type == 'VIP':
        return price * 0.2
    elif is_holiday:
        return price * 0.1
    else:
        return 0


def test_calculate_discount():
    # VIP customer on holiday
    assert calculate_discount(100, 'VIP', True) == 30
    # VIP customer not on holiday
    assert calculate_discount(100, 'VIP', False) == 20
    # Regular customer on holiday
    assert calculate_discount(100, 'Regular', True) == 10
    # Regular customer not on holiday
    assert calculate_discount(100, 'Regular', False) == 0
    # Zero price
    assert calculate_discount(0, 'VIP', True) == 0
    # Negative price
    assert calculate_discount(-50, 'VIP', True) == 0

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test starts	pytest test runner initialized	—	PASS
2	Calls calculate_discount(100, 'VIP', True)	Function evaluates conditions for VIP customer on holiday	Return value equals 30	PASS
3	Calls calculate_discount(100, 'VIP', False)	Function evaluates conditions for VIP customer not on holiday	Return value equals 20	PASS
4	Calls calculate_discount(100, 'Regular', True)	Function evaluates conditions for regular customer on holiday	Return value equals 10	PASS
5	Calls calculate_discount(100, 'Regular', False)	Function evaluates conditions for regular customer not on holiday	Return value equals 0	PASS
6	Calls calculate_discount(0, 'VIP', True)	Function evaluates zero price case	Return value equals 0	PASS
7	Calls calculate_discount(-50, 'VIP', True)	Function evaluates negative price case	Return value equals 0	PASS
8	Test ends	All assertions passed	—	PASS

Failure Scenario

Failing Condition: Function returns incorrect discount for VIP customer on holiday

Execution Trace Quiz - 3 Questions

What discount does a VIP customer get on a holiday for a price of 100?

A 10

B 20

C 30

D 0

Key Result

Using multiple conditions and test cases helps cover real-world scenarios, ensuring the function behaves correctly under complex rules.

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