Why integration tests verify components together in PyTest - Automation Benefits in Action

Verify integration of two components: UserService and EmailService

Preconditions (3)

Step 1: Create a UserService instance with a real EmailService instance

Step 2: Call UserService.register_user('[e-mail]')

Step 3: Check if EmailService sent a welcome email to '[e-mail]'

✅ Expected Result: EmailService sends a welcome email to the new user email address

Automation Requirements - pytest

Assertions Needed:

Assert that the email was sent to the correct address

Assert that the email content contains 'Welcome'

Best Practices:

Use fixtures to set up test objects

Avoid mocking the EmailService to test real integration

Use clear and descriptive assertion messages

Automated Solution

PyTest

import pytest

class EmailService:
    def __init__(self):
        self.sent_emails = []

    def send_email(self, to_address: str, content: str):
        self.sent_emails.append({'to': to_address, 'content': content})

class UserService:
    def __init__(self, email_service: EmailService):
        self.email_service = email_service

    def register_user(self, email: str):
        # Imagine user registration logic here
        welcome_message = f"Welcome, {email}!"
        self.email_service.send_email(email, welcome_message)

@pytest.fixture
def email_service():
    return EmailService()

@pytest.fixture
def user_service(email_service):
    return UserService(email_service)

def test_user_registration_sends_welcome_email(user_service, email_service):
    test_email = '[e-mail]'
    user_service.register_user(test_email)

    assert len(email_service.sent_emails) == 1, "Expected one email to be sent"
    sent_email = email_service.sent_emails[0]
    assert sent_email['to'] == test_email, f"Email sent to {sent_email['to']} instead of {test_email}"
    assert 'Welcome' in sent_email['content'], "Email content does not contain 'Welcome'"

This test checks that when UserService.register_user is called, it uses the EmailService to send a welcome email.

We create real instances of both services to verify their integration, not mocks, so we test the actual collaboration.

Fixtures set up the services cleanly for reuse.

Assertions check that exactly one email was sent, to the correct address, and that the content includes the word 'Welcome'.

This shows how integration tests verify components working together, not just isolated units.

Common Mistakes - 3 Pitfalls

Mocking EmailService completely and not verifying real email sending

Not asserting the email content or recipient

Using global state or shared EmailService instance across tests

Bonus Challenge

Now add data-driven testing with 3 different user emails to verify welcome emails are sent correctly for each.

Show Hint

Practice

1. Why do integration tests verify components together in pytest?

easy

A. To check if different parts of the program work well together

B. To test a single function in isolation

C. To measure the speed of the program

D. To check the spelling in the code comments

Solution

1. Step 1: Understand the purpose of integration tests

   Integration tests focus on testing how different parts or components of a program work together as a group.

2. Step 2: Compare with other test types

   Unit tests check single functions alone, while integration tests check combined parts to find issues missed by unit tests.

3. Final Answer:

   To check if different parts of the program work well together -> Option A

4. Quick Check:

   Integration tests verify combined components = A [OK]

Hint: Integration tests check combined parts, not single functions [OK]

Common Mistakes:

• Confusing integration tests with unit tests
• Thinking integration tests check performance
• Assuming integration tests check code comments

2. Which pytest code snippet correctly shows an integration test combining two components?

easy

A. def test_multiply(): assert multiply(2, 3) == 6

B. def test_add(): assert add(2, 3) == 5

C. def test_subtract(): assert subtract(5, 3) == 2

D. def test_add_and_multiply(): assert multiply(add(2, 3), 4) == 20

Solution

1. Step 1: Identify integration test code

   Integration tests combine multiple components; here, add and multiply are used together in one test.

2. Step 2: Check other options

   Options A, B, and D test single functions alone, so they are unit tests, not integration tests.

3. Final Answer:

   def test_add_and_multiply(): assert multiply(add(2, 3), 4) == 20 -> Option D

4. Quick Check:

   Integration test combines functions = C [OK]

Hint: Integration test calls multiple functions together [OK]

Common Mistakes:

• Choosing unit tests as integration tests
• Ignoring combined function calls
• Not checking the assertion logic

3. Given the pytest integration test below, what will be the test result?

def test_process_order():
    order = create_order(5)
    result = process_payment(order)
    assert result == 'Success'

medium

A. Test fails because create_order is not defined

B. Test passes if process_payment returns 'Success' for order 5

C. Test passes regardless of process_payment output

D. Test fails due to syntax error

Solution

1. Step 1: Analyze the test logic

   The test calls create_order and then process_payment with the order. It asserts the result equals 'Success'.

2. Step 2: Understand test pass condition

   If process_payment(order) returns 'Success', the assertion passes and the test passes. Otherwise, it fails.

3. Final Answer:

   Test passes if process_payment returns 'Success' for order 5 -> Option B

4. Quick Check:

   Assertion matches output = B [OK]

Hint: Test passes only if assertion matches actual output [OK]

Common Mistakes:

• Assuming test passes without matching assertion
• Confusing undefined functions with test result
• Thinking syntax error exists without checking code

4. Identify the error in this pytest integration test code:

def test_user_login():
    user = create_user('alice')
    assert login(user) == True
    assert logout(user) = True

medium

A. No error, code is correct

B. Missing parentheses in function calls

C. Using single equals (=) instead of double equals (==) in last assertion

D. Using wrong function names for login and logout

Solution

1. Step 1: Check assertion syntax

   The last assertion uses single equals (=) which is assignment, not comparison. It should be double equals (==).

2. Step 2: Verify other code parts

   Function calls have parentheses and function names look consistent. So no other syntax errors.

3. Final Answer:

   Using single equals (=) instead of double equals (==) in last assertion -> Option C

4. Quick Check:

   Use '==' for comparison in assertions = D [OK]

Hint: Assertions need '==' not '=' for comparisons [OK]

Common Mistakes:

• Confusing assignment (=) with comparison (==)
• Ignoring syntax errors in assertions
• Assuming function names cause error without evidence

5. You have two components: fetch_data() returns data list, and process_data(data) filters it. Why is an integration test combining both important?

hard

A. To verify process_data works correctly with actual fetched data

B. To check if fetch_data returns correct data format alone

C. To test process_data independently with mock data

D. To measure how fast fetch_data runs

Solution

1. Step 1: Understand component roles

   fetch_data() gets data, process_data(data) filters it. Testing them together checks real interaction.

2. Step 2: Why integration test matters here

   Integration test ensures process_data handles actual data from fetch_data, catching issues missed by isolated tests.

3. Final Answer:

   To verify process_data works correctly with actual fetched data -> Option A

4. Quick Check:

   Integration test checks real data flow = A [OK]

Hint: Integration tests check real data flow between components [OK]

Common Mistakes:

• Testing components only in isolation
• Ignoring real data format in integration
• Confusing performance test with integration test