-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Add documentation blurb for --strict #3558
Conversation
Feels out of place in there, plus the reference documentation already contains the reference API to all mark-related classes
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.
little tiny changes :) otherwise looks good
doc/en/mark.rst
Outdated
Raising errors on unknown marks: --strict | ||
----------------------------------------- | ||
|
||
The ``--strict`` command-line flag can be used to raise errors when marks not registered in the ``pytest.ini`` file. |
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.
how about
When the ``--strict`` command-line flag is passed, any marks not registered in the ``pytest.ini`` file will trigger an error.
or I guess, a one-word fix to the current phrasing would be to s/when marks not/when marks are not/
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 like yours better, thanks!
doc/en/mark.rst
Outdated
slow | ||
serial | ||
|
||
This can be used to prevent users mistyping mark names by accident. Test suites that want to enforce that this |
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.
s/that //
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.
Oops thanks
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.
LGTM, thanks!
As for pytest-django we are registering them like this: https://github.com/pytest-dev/pytest-django/blob/b93e0c556fe6c357dfc39363ed9cbe6b7e1e64c6/pytest_django/plugin.py#L187-L190
Great, thanks! @blueyed next time feel free to merge it yourself. 😁 |
Also remove Mark api from mark.rst: Feels out of place in there, plus the reference documentation already contains the reference API to all mark-related classes.
Fix #3549