@@ -927,6 +927,8 @@ doesn't guarantee a safe cleanup. That's covered in a bit more detail in
927927.. code-block :: pytest
928928
929929 $ pytest -q test_emaillib.py
930+ . [100%]
931+ 1 passed in 0.12s
930932
931933 Handling errors for yield fixture
932934"""""""""""""""""""""""""""""""""
@@ -1010,6 +1012,8 @@ does offer some nuances for when you're in a pinch.
10101012.. code-block :: pytest
10111013
10121014 $ pytest -q test_emaillib.py
1015+ . [100%]
1016+ 1 passed in 0.12s
10131017
10141018 .. _`safe teardowns` :
10151019
@@ -1062,6 +1066,8 @@ wouldn't be compact anymore).
10621066.. code-block :: pytest
10631067
10641068 $ pytest -q test_emaillib.py
1069+ . [100%]
1070+ 1 passed in 0.12s
10651071
10661072 .. _`safe fixture structure` :
10671073
@@ -1978,11 +1984,13 @@ Running the above tests results in the following test IDs being used:
19781984 platform linux -- Python 3.x.y, pytest-6.x.y, py-1.x.y, pluggy-0.x.y
19791985 cachedir: $PYTHON_PREFIX/.pytest_cache
19801986 rootdir: $REGENDOC_TMPDIR
1981- collected 10 items
1987+ collected 11 items
19821988
19831989 <Module test_anothersmtp.py>
19841990 <Function test_showhelo[smtp.gmail.com]>
19851991 <Function test_showhelo[mail.python.org]>
1992+ <Module test_emaillib.py>
1993+ <Function test_email_received>
19861994 <Module test_ids.py>
19871995 <Function test_a[spam]>
19881996 <Function test_a[ham]>
@@ -1994,7 +2002,7 @@ Running the above tests results in the following test IDs being used:
19942002 <Function test_ehlo[mail.python.org]>
19952003 <Function test_noop[mail.python.org]>
19962004
1997- ======================= 10 tests collected in 0.12s ========================
2005+ ======================= 11 tests collected in 0.12s ========================
19982006
19992007 .. _`fixture-parametrize-marks` :
20002008
0 commit comments