capsys for stdout/stderr in PyTest - Framework Patterns

Framework Mode - capsys for stdout/stderr

Folder Structure

project-root/
├── tests/
│   ├── test_example.py
│   ├── test_utils.py
│   └── conftest.py
├── src/
│   └── app_code.py
├── pytest.ini
└── requirements.txt
    

This structure keeps test files inside tests/ and application code inside src/. The conftest.py file holds shared fixtures and setup.

Test Framework Layers

• Test Cases: Individual test functions in tests/ using capsys to capture output.
• Fixtures: Shared setup in conftest.py, can provide reusable capsys usage if needed.
• Application Code: Code under test in src/.
• Utilities: Helper functions or classes to support tests.
• Configuration: pytest.ini for pytest settings.

Configuration Patterns

Use pytest.ini to configure pytest options like verbosity or markers.

Example pytest.ini:

[pytest]
addopts = -v
markers =
    slow: marks tests as slow
    smoke: marks smoke tests
    

Environment variables can be used to control test behavior if needed.

Test Reporting and CI/CD Integration

pytest outputs test results to the console by default, showing which tests passed or failed.

Use plugins like pytest-html to generate HTML reports for better visualization.

Integrate pytest runs into CI/CD pipelines (GitHub Actions, Jenkins, GitLab CI) by running pytest commands and collecting reports.

Best Practices

• Use capsys fixture to capture and assert output from stdout and stderr without modifying application code.
• Keep tests isolated; do not rely on output order or side effects outside the test scope.
• Use clear and descriptive assertion messages when checking captured output.
• Use capsys.readouterr() only once per test to avoid missing output.
• Combine capsys with parameterized tests to check multiple output scenarios efficiently.

Self Check

Where in this framework structure would you add a new test that verifies the output printed by a function?

Key Result

Use pytest's capsys fixture in test functions to capture and assert stdout and stderr output cleanly.

Practice

1. What is the main purpose of using capsys in pytest tests?

easy

A. To capture and check printed output sent to stdout and stderr

B. To speed up test execution by skipping print statements

C. To automatically fix syntax errors in print statements

D. To generate random test data for print output

Solution

1. Step 1: Understand what capsys does

   capsys is a pytest feature that captures output sent to the console, including both stdout and stderr.

2. Step 2: Identify its main use in tests

   It allows tests to check what was printed, so you can verify messages or errors your code produces.

3. Final Answer:

   To capture and check printed output sent to stdout and stderr -> Option A

4. Quick Check:

   capsys captures output = C [OK]

Hint: capsys catches print output for verification [OK]

Common Mistakes:

• Thinking capsys speeds up tests
• Believing capsys fixes code errors
• Confusing capsys with test data generation

2. Which of the following is the correct way to use capsys to capture printed output in a pytest test function?

easy

A. def test_func(capsys): captured = capsys.capture(); print('Hello')

B. def test_func(): capsys = print('Hello'); captured = capsys.readouterr()

C. def test_func(capsys): print('Hello'); captured = capsys.readouterr()

D. def test_func(): captured = capsys.readouterr(); print('Hello')

Solution

1. Step 1: Check how capsys is passed and used

   In pytest, capsys is passed as a function argument and used after printing to capture output.

2. Step 2: Verify correct method to read output

   The method to get output is capsys.readouterr(), which returns captured stdout and stderr.

3. Final Answer:

   def test_func(capsys): print('Hello'); captured = capsys.readouterr() -> Option C

4. Quick Check:

   capsys as argument + readouterr() = A [OK]

Hint: Pass capsys as argument and call readouterr() after print [OK]

Common Mistakes:

• Not passing capsys as a test function argument
• Calling non-existent capture() method
• Calling readouterr() before printing

3. What will be the output of the following pytest test code snippet?

def test_output(capsys):
    print('Test message')
    captured = capsys.readouterr()
    assert captured.out == 'Test message\n'

medium

A. Test passes because printed output matches assertion

B. Test fails because captured.out does not include newline

C. Test fails due to syntax error in print statement

D. Test fails because capsys.readouterr() is called before print

Solution

1. Step 1: Understand output capture timing

   The print statement runs first, sending 'Test message' plus a newline to stdout.

2. Step 2: Check captured output and assertion

   capsys.readouterr() captures the output including the newline. The assertion checks for 'Test message\n', which matches exactly.

3. Final Answer:

   Test passes because printed output matches assertion -> Option A

4. Quick Check:

   Printed output includes newline = B [OK]

Hint: Remember print adds newline; assert with '\n' [OK]

Common Mistakes:

• Forgetting newline in assertion string
• Calling readouterr() before print
• Assuming captured.out excludes newlines

4. Identify the error in this pytest test using capsys:

def test_error(capsys):
    captured = capsys.readouterr()
    print('Hello')
    assert captured.out == 'Hello\n'

medium

A. Missing parentheses in print statement

B. Calling capsys.readouterr() before printing captures nothing

C. Assertion string missing newline character

D. capsys must be imported before use

Solution

1. Step 1: Check order of output capture and print

   capsys.readouterr() is called before the print statement, so it captures output up to that point, which is empty.

2. Step 2: Understand assertion failure reason

   The assertion expects 'Hello\n' but captured.out is empty, causing test failure.

3. Final Answer:

   Calling capsys.readouterr() before printing captures nothing -> Option B

4. Quick Check:

   Read output after print, not before = A [OK]

Hint: Always call readouterr() after print to capture output [OK]

Common Mistakes:

• Calling readouterr() before print
• Forgetting newline in assertion
• Assuming capsys needs import

5. You want to test a function that prints error messages to stderr using pytest and capsys. Which code snippet correctly captures and asserts the stderr output?

hard

A. def test_error_message(capsys):
print('Error occurred', file=sys.stdout)
captured = capsys.readouterr()
assert captured.err == 'Error occurred\n'

B. def test_error_message(capsys):
print('Error occurred')
captured = capsys.readouterr()
assert captured.err == 'Error occurred\n'

C. def test_error_message():
print('Error occurred', file=sys.stderr)
captured = capsys.readouterr()
assert captured.err == 'Error occurred\n'

D. def test_error_message(capsys):
print('Error occurred', file=sys.stderr)
captured = capsys.readouterr()
assert captured.err == 'Error occurred\n'

Solution

1. Step 1: Identify how to print to stderr

   Use print(..., file=sys.stderr) to send output to stderr stream.

2. Step 2: Check correct use of capsys and assertion

   capsys.readouterr() captures both stdout and stderr. To check stderr, assert captured.err matches expected string including newline.

3. Final Answer:

   def test_error_message(capsys): print('Error occurred', file=sys.stderr) captured = capsys.readouterr() assert captured.err == 'Error occurred\n' -> Option D

4. Quick Check:

   Print to stderr + assert captured.err = D [OK]

Hint: Print with file=sys.stderr and assert captured.err [OK]

Common Mistakes:

• Not passing capsys as argument
• Printing to stdout instead of stderr
• Asserting captured.out instead of captured.err