Why capturing output validates behavior in PyTest - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to capture printed output in a pytest test function.

PyTest

def test_print_output(capsys):
    print('Hello, world!')
    captured = capsys.[1]()
    assert captured.out == 'Hello, world!\n'

Drag options to blanks, or click blank then click option'

Areadouterr

Bcapture

Cgetoutput

Dread

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-existent method like capsys.capture()

Trying to read output without calling a method

The capsys.readouterr() method captures the output printed to stdout and stderr during the test.

2fill in blank

medium

Complete the assertion to check that the captured output contains the expected substring.

PyTest

def test_partial_output(capsys):
    print('Test output for pytest')
    captured = capsys.readouterr()
    assert [1] in captured.out

Drag options to blanks, or click blank then click option'

A'pytest'

Bcaptured.out

C'output'

D'fail'

Attempts:

3 left

💡 Hint

Common Mistakes

Checking for a string not present in the output

Using the whole output instead of a substring

We check that the string 'pytest' is part of the captured output.

3fill in blank

hard

Fix the error in the test code to correctly capture and assert printed output.

PyTest

def test_error_output(capsys):
    print('Error occurred')
    captured = capsys.[1]()
    assert captured.err == ''

Drag options to blanks, or click blank then click option'

Areadouterror

Breadouterr

Creadoutput

Dcapture

Attempts:

3 left

💡 Hint

Common Mistakes

Misspelling the method name

Using a method that does not exist

The correct method to capture output is readouterr(). It returns both stdout and stderr.

4fill in blank

hard

Fill both blanks to capture output and assert it matches the expected string.

PyTest

def test_output_match(capsys):
    print('Success!')
    captured = capsys.[1]()
    assert captured.[2] == 'Success!\n'

Drag options to blanks, or click blank then click option'

Areadouterr

Bout

Cerr

Dcapture

Attempts:

3 left

💡 Hint

Common Mistakes

Checking captured.err instead of captured.out

Using a wrong method name for capturing

Use readouterr() to capture output and check captured.out for stdout content.

5fill in blank

hard

Fill all three blanks to capture output, strip whitespace, and assert the exact message.

PyTest

def test_strip_output(capsys):
    print('  Trim me  ')
    captured = capsys.[1]()
    output = captured.[2].[3]()
    assert output == 'Trim me'

Drag options to blanks, or click blank then click option'

Areadouterr

Bout

Cstrip

Drstrip

Attempts:

3 left

💡 Hint

Common Mistakes

Using rstrip() which only removes trailing spaces

Forgetting to call the method with parentheses

We capture output with readouterr(), access out, then use strip() to remove spaces.

Practice

1. Why is capturing output useful in pytest when testing a function that prints messages?

easy

A. It automatically fixes errors in the printed output.

B. It speeds up the test execution by skipping print statements.

C. It lets you check the printed messages to confirm correct behavior.

D. It prevents the function from running during tests.

Solution

1. Step 1: Understand output capturing purpose

   Capturing output allows tests to see what the function prints, which is important to verify expected messages.

2. Step 2: Relate to behavior validation

   By checking printed messages, we confirm the function behaves as intended, not just runs without errors.

3. Final Answer:

   It lets you check the printed messages to confirm correct behavior. -> Option C

4. Quick Check:

   Output capture = verify printed messages [OK]

Hint: Output capture checks printed text to confirm behavior [OK]

Common Mistakes:

• Thinking output capture speeds tests
• Believing it fixes errors automatically
• Assuming it stops function execution

2. Which pytest fixture is used to capture output printed by a function during a test?

easy

A. capsys

B. capout

C. capprint

D. capture

Solution

1. Step 1: Recall pytest output capture fixtures

   pytest provides the fixture named capsys to capture stdout and stderr output during tests.

2. Step 2: Eliminate incorrect options

   Other options like capout, capprint, and capture are not valid pytest fixtures.

3. Final Answer:

   capsys -> Option A

4. Quick Check:

   Output capture fixture = capsys [OK]

Hint: Remember pytest fixture for output capture is capsys [OK]

Common Mistakes:

• Using non-existent fixture names
• Confusing capsys with capture
• Misspelling the fixture name

3. Given this pytest test code, what will be the assertion result?

def greet():
    print('Hello, Tester!')

def test_greet(capsys):
    greet()
    captured = capsys.readouterr()
    assert captured.out == 'Hello, Tester!\n'

medium

A. The assertion fails because output is missing a newline.

B. The assertion passes because output matches exactly.

C. The assertion fails because output includes extra spaces.

D. The test raises an error due to incorrect capsys usage.

Solution

1. Step 1: Analyze printed output from greet()

   The function prints 'Hello, Tester!' followed by a newline automatically from print().

2. Step 2: Check captured output and assertion

   capsys.readouterr() captures stdout including the newline, so captured.out equals 'Hello, Tester!\n', matching the assertion.

3. Final Answer:

   The assertion passes because output matches exactly. -> Option B

4. Quick Check:

   Printed output with newline = assertion match [OK]

Hint: Remember print adds newline; capture includes it [OK]

Common Mistakes:

• Forgetting print adds newline
• Comparing without newline in assertion
• Misusing capsys.readouterr()

4. Identify the error in this pytest test that uses output capture:

def say_hi():
    print('Hi!')

def test_say_hi(capsys):
    say_hi()
    captured = capsys.readouterr()
    assert captured.out == 'Hi!'

medium

A. The assertion misses the newline character at the end of output.

B. capsys fixture is not passed to the test function.

C. The function say_hi() does not print anything.

D. capsys.readouterr() should be called before say_hi().

Solution

1. Step 1: Understand print output format

   print('Hi!') outputs 'Hi!' plus a newline character '\n' at the end.

2. Step 2: Check assertion string against captured output

   The assertion compares captured.out to 'Hi!' without the newline, causing it to fail.

3. Final Answer:

   The assertion misses the newline character at the end of output. -> Option A

4. Quick Check:

   Print adds newline; assertion must include it [OK]

Hint: Always include newline in output assertions [OK]

Common Mistakes:

• Ignoring newline added by print
• Calling capsys.readouterr() too early
• Not passing capsys fixture to test

5. You want to test a function that prints different messages based on input. Which pytest approach best validates its behavior using output capture?

def respond(answer):
    if answer == 'yes':
        print('Confirmed')
    else:
        print('Denied')

hard

A. Replace print statements with return statements and assert return values without output capture.

B. Call respond('yes') and respond('no') without capturing output, then assert return values.

C. Use capsys to capture output once after both calls, then assert combined output equals 'ConfirmedDenied'.

D. Call respond('yes'), capture output with capsys, assert output is 'Confirmed\n', then repeat for 'no' with 'Denied\n'.

Solution

1. Step 1: Understand output capture per call

   Each call to respond prints a message; capturing output after each call separately lets us check exact printed text.

2. Step 2: Validate output for each input

   Calling respond('yes') should print 'Confirmed\n', and respond('no') should print 'Denied\n'. Separate captures and assertions confirm correct behavior.

3. Final Answer:

   Call respond('yes'), capture output with capsys, assert output is 'Confirmed\n', then repeat for 'no' with 'Denied\n'. -> Option D

4. Quick Check:

   Separate capture/assert per call = correct validation [OK]

Hint: Capture output separately for each function call [OK]

Common Mistakes:

• Capturing output once for multiple calls
• Asserting combined output without newlines
• Ignoring output capture and checking return values