Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/en/how-to/capture-stdout-stderr.rst
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,7 @@ test from having to care about setting/resetting
output streams and also interacts well with pytest's
own per-test capturing.

The return value from ``readouterr`` changed to a ``namedtuple`` with two attributes, ``out`` and ``err``.
The return value of ``readouterr()`` is a ``namedtuple`` with two attributes, ``out`` and ``err``.

If the code under test writes non-textual data (``bytes``), you can capture this using
the :fixture:`capsysbinary` fixture which instead returns ``bytes`` from
Expand Down
4 changes: 0 additions & 4 deletions doc/en/how-to/parametrize.rst
Original file line number Diff line number Diff line change
Expand Up @@ -29,10 +29,6 @@ pytest enables test parametrization at several levels:

.. regendoc: wipe



Several improvements.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another leftover I noticed when reviewing the original commit. I think it got hidden as a comment because it's intended under the .. regendoc: wipe.

The builtin :ref:`pytest.mark.parametrize ref` decorator enables
parametrization of arguments for a test function. Here is a typical example
of a test function that implements checking that a certain input leads
Expand Down