p53209761
/
test_ok2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix issue439: clarify that capsys/capfd capture output during 

test execution, not test setup.
This commit is contained in:
holger krekel 2014-04-07 13:42:48 +02:00
parent 6efde60b8b
commit e382ed4245
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/en/capture.txt
View File

@ -84,11 +84,9 @@ of the failing function and hide the other one::
Accessing captured output from a test function Accessing captured output from a test function
--------------------------------------------------- ---------------------------------------------------
The :ref:`funcarg mechanism` allows test function a very easy The ``capsys`` and ``capfd`` fixtures allow to access stdout/stderr
way to access the captured output by simply using the names output created during test execution. Here is an example test function
``capsys`` or ``capfd`` in the test function signature. Here that performs some output related checks::
is an example test function that performs some output related
checks::
def test_myoutput(capsys): # or use "capfd" for fd-level def test_myoutput(capsys): # or use "capfd" for fd-level
print ("hello") print ("hello")
@ -108,8 +106,10 @@ test from having to care about setting/resetting
output streams and also interacts well with pytest's output streams and also interacts well with pytest's
own per-test capturing. own per-test capturing.
If you want to capture on ``fd`` level you can use If you want to capture on filedescriptor level you can use
the ``capfd`` function argument which offers the exact the ``capfd`` function argument which offers the exact
same interface. same interface but allows to also capture output from
libraries or subprocesses that directly write to operating
system level output streams (FD1 and FD2).
.. include:: links.inc .. include:: links.inc