p53209761
/
test_ok2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Feanil Patel 2021-02-19 13:46:29 -05:00 committed by GitHub
parent a44dcf5ece
commit e6012612b9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/en/fixture.rst
View File

@ -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 arguments, as in the ``test_my_fruit_in_basket(my_fruit, fruit_basket):`` in the
previous example. 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 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 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 those parameters. Once pytest finds them, it runs those fixtures, captures what