Skip to content
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

Further "unknown marks warning" improvements #5023

Closed
nicoddemus opened this issue Apr 2, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@nicoddemus
Copy link
Member

commented Apr 2, 2019

As discussed in #4935 and #4935 (comment):

  • Add --strict-marks as an alias to --strict, and use --strict-marks in the documentation and examples;
  • Remove the various marks that are used through testing: foo, bar, multiple spellings of parametrize, etc.
  • After the above, we should try to get rid of UnknownMarksWarning in favor of PytestWarning; if not, we should then create more subclasses of PytestWarning for the other warnings emitted by pytest.
  • Add integration tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.