Why Log level filtering in PyTest? - Purpose & Use Cases

The Big Idea

What if you could instantly see only the errors in your test logs without endless scrolling?

The Scenario

Imagine running a test suite that produces hundreds of log messages. You try to find important errors by scrolling through endless info and debug messages.

The Problem

Manually scanning logs is slow and tiring. You might miss critical errors hidden among less important messages. It's easy to get overwhelmed and frustrated.

The Solution

Log level filtering lets you automatically show only the messages you care about, like errors or warnings. This saves time and helps you focus on real problems.

Before vs After

✗ Before

print(all logs, then search manually for 'ERROR')

✓ After

pytest --log-cli-level=ERROR  # shows only error logs during tests

What It Enables

It enables quick spotting of critical issues by filtering out noise in test logs.

Real Life Example

When testing a web app, you only want to see error logs to fix crashes, not every info message about user clicks.

Key Takeaways

Manual log checking is slow and error-prone.

Log level filtering automatically shows important messages.

This helps testers find and fix bugs faster.

Practice

1. What does caplog.at_level() do in pytest?

easy

A. It sets the minimum log level to capture during a test.

B. It clears all captured logs before the test runs.

C. It disables logging for the entire test session.

D. It changes the log message format.

Solution

1. Step 1: Understand caplog usage

   caplog is a pytest fixture used to capture log messages during tests.

2. Step 2: Purpose of at_level()

   The method at_level() sets the minimum log level to capture, filtering out lower-level messages.

3. Final Answer:

   It sets the minimum log level to capture during a test. -> Option A

4. Quick Check:

   caplog.at_level() sets log capture level [OK]

Hint: Remember: at_level sets minimum log level to capture [OK]

Common Mistakes:

• Thinking it clears logs instead of setting level
• Confusing it with disabling logging
• Assuming it changes log format

2. Which of the following is the correct syntax to capture only WARNING and above logs in pytest using caplog?

easy

A. with caplog.at_level(logging.WARNING):

B. with caplog.set_level(logging.WARNING):

C. caplog.at_level = logging.WARNING

D. caplog.capture_level(logging.WARNING)

Solution

1. Step 1: Identify correct method usage

   The correct method to set log level context is caplog.at_level() used with with statement.

2. Step 2: Check syntax correctness

   with caplog.at_level(logging.WARNING): uses with caplog.at_level(logging.WARNING): which is the documented and correct syntax.

3. Final Answer:

   with caplog.at_level(logging.WARNING): -> Option A

4. Quick Check:

   Use with caplog.at_level(level) for filtering [OK]

Hint: Use 'with caplog.at_level(level):' to filter logs [OK]

Common Mistakes:

• Using assignment instead of context manager
• Using non-existent methods like set_level or capture_level
• Missing the with statement

3. Given the code below, what log messages will be captured?

import logging

def test_logs(caplog):
    with caplog.at_level(logging.ERROR):
        logging.warning('Warning message')
        logging.error('Error message')
    return caplog.records

medium

A. Both 'Warning message' and 'Error message' are captured.

B. Only 'Warning message' is captured.

C. Only 'Error message' is captured.

D. No messages are captured.

Solution

1. Step 1: Understand log level filtering

   Setting caplog.at_level(logging.ERROR) captures logs at ERROR level or higher only.

2. Step 2: Analyze logged messages

   Warning is below ERROR level, so it is ignored. Error message is at ERROR level, so it is captured.

3. Final Answer:

   Only 'Error message' is captured. -> Option C

4. Quick Check:

   ERROR level filters out WARNING [OK]

Hint: Only logs at or above set level appear [OK]

Common Mistakes:

• Assuming WARNING logs appear when level is ERROR
• Thinking all logs are captured regardless of level
• Confusing ERROR and WARNING levels

4. Identify the error in the following pytest test code using caplog:

def test_example(caplog):
    caplog.at_level(logging.INFO)
    logging.debug('Debug message')
    logging.info('Info message')
    assert 'Info message' in caplog.text

medium

A. The assert statement syntax is incorrect.

B. caplog.at_level() must be used as a context manager with 'with'.

C. caplog.text does not exist; use caplog.records instead.

D. Logging messages must be uppercase strings.

Solution

1. Step 1: Check caplog.at_level usage

   The method at_level() must be used with a with statement to set the log level context.

2. Step 2: Identify the error

   Calling caplog.at_level(logging.INFO) without with does not set the level properly, so logs may not be filtered as expected.

3. Final Answer:

   caplog.at_level() must be used as a context manager with 'with'. -> Option B

4. Quick Check:

   Use 'with caplog.at_level(level):' always [OK]

Hint: Always use 'with' when calling caplog.at_level() [OK]

Common Mistakes:

• Calling at_level() without 'with' statement
• Assuming caplog.text is invalid (it exists)
• Thinking assert syntax is wrong

5. You want to test a function that logs messages at DEBUG, INFO, and ERROR levels. You only want to capture INFO and ERROR logs but exclude DEBUG. Which pytest code snippet correctly sets this up?

hard

A. with caplog.at_level(logging.ERROR):
func()
assert 'INFO message' in caplog.text

B. with caplog.at_level(logging.DEBUG):
func()
assert 'INFO message' in caplog.text

C. with caplog.at_level(logging.INFO):
func()
assert 'DEBUG message' in caplog.text

D. with caplog.at_level(logging.INFO):
func()
assert 'DEBUG message' not in caplog.text

Solution

1. Step 1: Determine log levels to capture

   Setting caplog.at_level(logging.INFO) captures INFO and ERROR logs but excludes DEBUG logs.

2. Step 2: Verify assertions

   with caplog.at_level(logging.INFO): func() assert 'DEBUG message' not in caplog.text asserts DEBUG messages are not in captured logs, which matches the requirement.

3. Final Answer:

   with caplog.at_level(logging.INFO): func() assert 'DEBUG message' not in caplog.text -> Option D

4. Quick Check:

   Set level INFO to exclude DEBUG logs [OK]

Hint: Set level to INFO to exclude DEBUG logs [OK]

Common Mistakes:

• Setting level too low and capturing DEBUG logs
• Setting level too high and missing INFO logs
• Wrong assertion about presence of DEBUG logs