diff options
| author | Bruno Oliveira <nicoddemus@gmail.com> | 2021-02-05 15:11:17 -0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-02-05 15:11:17 -0300 |
| commit | 150bdceb7ac073800a3dff2fe6a017c61992b46f (patch) | |
| tree | 2d29d1451619ea1f05abce384179703f1bdbceaf | |
| parent | ed8cabe4fdbfe2068d385dfcc6618551810b7d54 (diff) | |
| parent | c604f3f0c52b51fc61ba7d208d522c2614aaa10d (diff) | |
| download | pytest-150bdceb7ac073800a3dff2fe6a017c61992b46f.tar.gz | |
Merge pull request #8322 from pytest-dev/fixture-docs
doc: Remove confusing fixture sentence
| -rw-r--r-- | doc/en/fixture.rst | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/doc/en/fixture.rst b/doc/en/fixture.rst index d72a0e619..6ffd77920 100644 --- a/doc/en/fixture.rst +++ b/doc/en/fixture.rst @@ -174,9 +174,6 @@ Back to fixtures "Fixtures", in the literal sense, are each of the **arrange** steps and data. They're 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 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 |