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

doc: Remove confusing fixture sentence 

There is no previous `test_ehlo` example (it follows much later) - and the same thing is described further down in ""Requesting" fixtures" already.
This commit is contained in:
Florian Bruhin 2021-02-05 17:47:37 +01:00 committed by GitHub
parent ed8cabe4fd
commit c604f3f0c5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/en/fixture.rst
View File

@ -174,9 +174,6 @@ Back to fixtures
"Fixtures", in the literal sense, are each of the **arrange** steps and data. They're "Fixtures", in the literal sense, are each of the **arrange** steps and data. They're
everything that test needs to do its thing. everything that test needs to do its thing.
At a basic level, test functions request fixtures by declaring them as
arguments, as in the ``test_ehlo(smtp_connection):`` in the previous example.
In pytest, "fixtures" are functions you define that serve this purpose. But they In pytest, "fixtures" are functions you define that serve this purpose. But they
don't have to be limited to just the **arrange** steps. They can provide the don't have to be limited to just the **arrange** steps. They can provide the
**act** step, as well, and this can be a powerful technique for designing more **act** step, as well, and this can be a powerful technique for designing more