floraachy
/
pytest2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

rework examples and edit copy

This commit is contained in:
Adrián Aizpurua 2022-07-27 19:55:50 +02:00
parent 059447cecd
commit fd316339ed
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/en/how-to/fixtures.rst
View File

@ -741,8 +741,8 @@ does offer some nuances for when you're in a pinch.
Note on finalizer order
""""""""""""""""""""""""
Finalizers are executed in a first-in-last-out order, while operations after yield are executed sequentially.
Consider the differences in the following examples:
Finalizers are executed in a first-in-last-out order.
For yield fixtures, the first fixture to run is the right-most one, i.e. the last test parameter.
.. regendoc:wipe
@ -751,7 +751,6 @@ Consider the differences in the following examples:
import pytest
@pytest.fixture
def test_bar(fix_w_yield1, fix_w_yield2):
print("test_bar")
@ -780,6 +779,9 @@ Consider the differences in the following examples:
after_yield_1
For finalizers, the first fixture to run is last call to `request.addfinalizer`.
.. code-block:: python
import pytest
@ -791,7 +793,6 @@ Consider the differences in the following examples:
request.addfinalizer(partial(print, "finalizer_1"))
@pytest.fixture
def test_bar(fix_w_finalizers):
print("test_bar")
@ -807,6 +808,8 @@ Consider the differences in the following examples:
.finalizer_1
finalizer_2
This is so because yield fixtures use addfinalizer behind the scenes: when the fixture executes, addfinalizer registers a function that resumes the generator, which in turn calls the teardown code.
.. _`safe teardowns`: