Skip to content

Commit

Permalink
#2692: Document setup/teardown behaviour when using unittest-based su…
Browse files Browse the repository at this point in the history
…ites
  • Loading branch information
OwenTuz committed Oct 21, 2017
1 parent 4cb60da commit 3cdbb18
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions doc/en/unittest.rst
Original file line number Diff line number Diff line change
Expand Up @@ -233,3 +233,13 @@ was executed ahead of the ``test_method``.
overwrite ``unittest.TestCase`` ``__call__`` or ``run``, they need to
to overwrite ``debug`` in the same way (this is also true for standard
unittest).

.. note::

Due to architectural differences between the two frameworks, setup and
teardown for ``unittest``-based tests is performed during the ``call`` phase
of testing instead of in ``pytest``'s standard ``setup`` and ``teardown``
stages. This can be important to understand in some situations, particularly
when reasoning about errors. For example, if a ``unittest``-based suite
exhibits errors during setup, ``pytest`` will report no errors during its
``setup`` phase and will instead raise the error during ``call``.

0 comments on commit 3cdbb18

Please sign in to comment.