-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix showing DeprecationWarnings for functional tests #7665
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
Conversation
Pull Request Test Coverage Report for Build 3307778080
💛 - Coveralls |
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.
Thank you for the fix, that was my bad !
042e05f
to
15a2242
Compare
@Pierre-Sassoulas Seems like you accidentally dismissed the approval. |
(I'm planning on creating a standalone pylint testutil package that would be properly tested, I don't dare to tell when 😄 I need adminship in pycka or a pylint organisation first) |
It seems I'm able to create a new repo in the PyCQA org. You should also be able to already. Just to clarify, this is just a helper package for running functional tests? The tests themself will stay here? |
It would be the current content of |
Description
The
recwarn
fixture fortest_functional
prevents allDeprecationWarnings
from showing up which aren't triggered at import. Noticed while working on a DeprecationWarning for pylint-dev/astroid#1389.The previous code was added in e37bf8c.
Refs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html#warns