From 6e687c4354f5bb6dd156e2a7fc54c79428962826 Mon Sep 17 00:00:00 2001 From: Xixi Zhao Date: Tue, 23 Jul 2019 15:09:32 +0800 Subject: [PATCH] Doc fix: m1 isn't a dependency of f1. According to the file in `example/fixtures/test_fixtures_order.py`, m1 isn't a dependency of f1. --- doc/en/fixture.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/en/fixture.rst b/doc/en/fixture.rst index 78fef13e8..d6c7bfd4d 100644 --- a/doc/en/fixture.rst +++ b/doc/en/fixture.rst @@ -307,7 +307,6 @@ The fixtures requested by ``test_foo`` will be instantiated in the following ord 1. ``s1``: is the highest-scoped fixture (``session``). 2. ``m1``: is the second highest-scoped fixture (``module``). - because it is a dependency of ``f1``. 3. ``a1``: is a ``function``-scoped ``autouse`` fixture: it will be instantiated before other fixtures within the same scope. 4. ``f3``: is a ``function``-scoped fixture, required by ``f1``: it needs to be instantiated at this point @@ -501,7 +500,7 @@ of a fixture is needed multiple times in a single test. Instead of returning data directly, the fixture instead returns a function which generates the data. This function can then be called multiple times in the test. -Factories can have have parameters as needed:: +Factories can have parameters as needed:: @pytest.fixture def make_customer_record():