Assert with messages in PyTest

Introduction

Assertions check if something is true in tests. Adding messages helps explain what went wrong if the test fails.

When you want to know why a test failed quickly.

When multiple checks are in one test and you need clear failure reasons.

When sharing tests with others who need clear feedback.

When debugging tests to save time understanding errors.

Syntax

PyTest

assert condition, "message"

The message shows only if the assertion fails.

Use clear, simple messages to explain the failure.

Examples

This assertion will pass silently because 2 + 2 equals 4.

PyTest

assert 2 + 2 == 4, "Math is broken!"

This checks if 'a' is in 'cat'. It passes silently.

PyTest

assert 'a' in 'cat', "Letter 'a' not found in word"

This will fail and show the message "Five is not greater than ten".

PyTest

assert 5 > 10, "Five is not greater than ten"

Sample Program

This test checks three conditions about the variable number. The first two pass, but the last fails and shows the message.

PyTest

def test_number():
    number = 10
    assert number > 5, "Number should be greater than 5"
    assert number < 20, "Number should be less than 20"
    assert number != 10, "Number should not be exactly 10"

Important Notes

Assertion messages help quickly find the problem without guessing.

Keep messages short and clear, like a helpful note.

Use assert messages especially in bigger tests with many checks.

Summary

Assertions check if something is true in tests.

Adding messages explains why a test failed.

Use clear messages to save time debugging.

Practice

1. What is the main purpose of adding a message to an assert statement in pytest?

easy

A. To explain why the test failed when the assertion is false

B. To make the test run faster

C. To skip the test if the assertion fails

D. To change the test result to pass automatically

Solution

1. Step 1: Understand the role of assert messages

   Assert messages provide extra information when a test fails, helping to understand the failure reason.

2. Step 2: Identify the purpose in pytest

   In pytest, messages after assert statements show in the test report only if the assertion fails, clarifying the problem.

3. Final Answer:

   To explain why the test failed when the assertion is false -> Option A

4. Quick Check:

   Assert message = failure explanation [OK]

Hint: Assert messages explain failures clearly [OK]

Common Mistakes:

• Thinking assert messages speed up tests
• Believing messages skip tests
• Assuming messages change test results

2. Which of the following is the correct syntax to add a message to an assert statement in pytest?

easy

A. assert(x == 5) : "x should be 5"

B. assert x == 5, "x should be 5"

C. assert x == 5 then "x should be 5"

D. assert x == 5 => "x should be 5"

Solution

1. Step 1: Recall Python assert syntax

   Python assert statements use a comma to separate the condition and the message: assert condition, message.

2. Step 2: Match with pytest usage

   pytest uses the same syntax, so assert x == 5, "x should be 5" is correct.

3. Final Answer:

   assert x == 5, "x should be 5" -> Option B

4. Quick Check:

   Assert syntax uses comma for message [OK]

Hint: Use comma after condition for assert message [OK]

Common Mistakes:

• Using colon or arrow instead of comma
• Adding message without comma
• Using parentheses incorrectly

3. What will be the output when running this pytest code?

def test_value():
    x = 3
    assert x == 5, "x is not equal to 5"

medium

A. Test passes silently

B. Test skipped automatically

C. SyntaxError due to assert message

D. Test fails with message: x is not equal to 5

Solution

1. Step 1: Check the assertion condition

   The variable x is 3, but the assertion expects x == 5, which is false.

2. Step 2: Understand pytest behavior on failed assert

   pytest will fail the test and show the message "x is not equal to 5" to explain the failure.

3. Final Answer:

   Test fails with message: x is not equal to 5 -> Option D

4. Quick Check:

   False assert triggers failure message [OK]

Hint: Failed assert shows message in pytest output [OK]

Common Mistakes:

• Assuming test passes despite false assert
• Expecting syntax error from message
• Thinking test skips automatically

4. Identify the error in this pytest assertion:

def test_check():
    y = 10
    assert y > 5 "y should be greater than 5"

medium

A. Missing comma between condition and message

B. Wrong comparison operator

C. Variable y is not defined

D. Message should be inside parentheses

Solution

1. Step 1: Review assert syntax

   Assert statements require a comma between the condition and the message string.

2. Step 2: Locate the syntax error

   The code misses a comma after y > 5, causing a syntax error.

3. Final Answer:

   Missing comma between condition and message -> Option A

4. Quick Check:

   Comma separates assert condition and message [OK]

Hint: Always put a comma before assert message [OK]

Common Mistakes:

• Forgetting comma after condition
• Adding parentheses around message
• Changing comparison operator unnecessarily

5. You want to test a function that returns a list of even numbers from 1 to 5. Which assert statement with a message best helps debug if the test fails?

def get_evens():
    return [2, 4]

def test_evens():
    result = get_evens()
    # Choose the best assert with message

hard

A. assert result == [2, 4], "Check the function"

B. assert result == [2, 4], "Test failed"

C. assert result == [2, 4], f"Expected [2, 4], got {result}"

D. assert result == [2, 4], f"Result is {result}"

Solution

1. Step 1: Understand the purpose of assert messages

   Good messages explain exactly what was expected and what was received to help debugging.

2. Step 2: Compare options for clarity

   assert result == [2, 4], f"Expected [2, 4], got {result}" uses an f-string to show both expected and actual results clearly, aiding quick diagnosis.

3. Final Answer:

   assert result == [2, 4], f"Expected [2, 4], got {result}" -> Option C

4. Quick Check:

   Clear message shows expected vs actual [OK]

Hint: Show expected and actual values in assert message [OK]

Common Mistakes:

• Using vague messages without details
• Not showing actual result in message
• Ignoring helpful f-string formatting