summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFeanil Patel <feanil@gmail.com>2021-02-19 13:46:29 -0500
committerGitHub <noreply@github.com>2021-02-19 13:46:29 -0500
commite6012612b9a7fe2ef6a6c5f46b95855d5977d438 (patch)
tree3eebdd91e82767e1e41e274b011a683b6786229c
parenta44dcf5ece3ecfc911a340f3721199fcf309ab65 (diff)
downloadpytest-e6012612b9a7fe2ef6a6c5f46b95855d5977d438.tar.gz
Remove a redundant paragraph
doc This paragraph looks like it is a more verbose version of the sentence right above it. Removing it doesn't reduce the amount of information here but does make the section flow a little better.
-rw-r--r--doc/en/fixture.rst6
1 files changed, 0 insertions, 6 deletions
diff --git a/doc/en/fixture.rst b/doc/en/fixture.rst
index 6ffd77920..028786f65 100644
--- a/doc/en/fixture.rst
+++ b/doc/en/fixture.rst
@@ -228,12 +228,6 @@ At a basic level, test functions request fixtures by declaring them as
arguments, as in the ``test_my_fruit_in_basket(my_fruit, fruit_basket):`` in the
previous example.
-At a basic level, pytest depends on a test to tell it what fixtures it needs, so
-we have to build that information into the test itself. We have to make the test
-"**request**" the fixtures it depends on, and to do this, we have to
-list those fixtures as parameters in the test function's "signature" (which is
-the ``def test_something(blah, stuff, more):`` line).
-
When pytest goes to run a test, it looks at the parameters in that test
function's signature, and then searches for fixtures that have the same names as
those parameters. Once pytest finds them, it runs those fixtures, captures what