-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Add reference docs for pytest.mark.usefixtures #3663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
nicoddemus
merged 2 commits into
pytest-dev:master
from
nicoddemus:usefixtures-reference
Jul 7, 2018
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -161,6 +161,25 @@ Skip a test function if a condition is ``True``. | |
:keyword str reason: Reason why the test function is being skipped. | ||
|
||
|
||
.. _`pytest.mark.usefixtures ref`: | ||
|
||
pytest.mark.usefixtures | ||
~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
**Tutorial**: :ref:`usefixtures`. | ||
|
||
Mark a test function as using the given fixture names. | ||
|
||
.. warning:: | ||
|
||
This mark can be used with *test functions* only, having no affect when applied | ||
to a **fixture** function. | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. perfect :) |
||
.. py:function:: pytest.mark.usefixtures(*names) | ||
|
||
:param args: the names of the fixture to use, as strings | ||
|
||
|
||
.. _`pytest.mark.xfail ref`: | ||
|
||
pytest.mark.xfail | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if it could be a good idea to add an explicit warning/reminder here that you can only mark test functions like this and not other fixtures to address #1014
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh good idea, will do
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something like:
"Be aware that although you can use fixtures from oher fixtures by adding them to the function parameters, you can not do this by marking the fixture function with
usefixtures
."Maybe even with an example?
This works:
This will not yield the wanted result and currently not result in an error or a warning either.
I would even suggest to put this in a warning box, because this can be surprising even for experienced pytest users, especially due to the lack of an error atm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @obestwalter!
I added the warning but the example I added to the tutorial/normal documentation. IMHO we should keep the reference as lean as possible.