Writing a pytest function for checking the output on console (stdout)
Use the capfd
fixture.
Example:
def test_foo(capfd):
foo() # Writes "Hello World!" to stdout
out, err = capfd.readouterr()
assert out == "Hello World!"
See: http://pytest.org/en/latest/fixture.html for more details
And see: py.test --fixtures
for a list of builtin fixtures.
Your example has a few problems. Here is a corrected version:
def f(name):
print "hello {}".format(name)
def test_f(capfd):
f("Tom")
out, err = capfd.readouterr()
assert out == "hello Tom\n"
Note:
- Do not use
sys.stdout
-- Use thecapfd
fixture as-is as provided by pytest. - Run the test with:
py.test foo.py
Test Run Output:
$ py.test foo.py
====================================================================== test session starts ======================================================================
platform linux2 -- Python 2.7.5 -- pytest-2.4.2
plugins: flakes, cache, pep8, cov
collected 1 items
foo.py .
=================================================================== 1 passed in 0.01 seconds ====================================================================
Also Note:
- You do not need to run your Test Function(s) in your test modules.
py.test
(The CLI tool and Test Runner) does this for you.
py.test does mainly three things:
- Collect your tests
- Run your tests
- Display statistics and possibly errors
By default py.test
looks for (configurable iirc) test_foo.py
test modules and test_foo()
test functions in your test modules.
The problem is with your explicit call of your test function at the very end of your first code snippet block:
test_add(sys.stdout)
You should not do this; it is pytest's job to call your test functions.
When it does, it will recognize the name capsys
(or capfd
, for that matter)
and automatically provide a suitable pytest-internal object for you as a call argument.
(The example given in the pytest documentation is quite complete as it is.)
That object will provide the required readouterr()
function.
sys.stdout
does not have that function, which is why your program fails.