Repository navigation
RemovedInPytest4Warning with pytest 3.8.0 #300
Description
I'm submitting a ...
- bug report
- feature request
- support request => Please do not submit support request here, see note at the top of this template.
What is the current behavior?
Using allure-pytest with the latest version of pytest results in deprecation warnings.
Similar to: #291
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
No deprecation warnings.
What is the motivation / use case for changing the behavior?
These warnings are numerous and should not be impeding testing/development.
Please tell us about your environment:
allure-pytest==2.5.2
allure-python-commons==2.5.2
pytest==3.8.2
Other information
Example warnings:
/lib/python2.7/site-packages/allure_pytest/utils.py:23: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly.
Please use node.get_closest_marker(name) or node.iter_markers(name).
Docs: https://docs.pytest.org/en/latest/mark.html#updating-code
return marker.args[0] if marker and marker.args else None
/lib/python2.7/site-packages/allure_pytest/utils.py:74: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly.
Please use node.get_closest_marker(name) or node.iter_markers(name).
Docs: https://docs.pytest.org/en/latest/mark.html#updating-code
args = [represent(arg) for arg in marker.args]
/lib/python2.7/site-packages/allure_pytest/utils.py:75: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly.
Please use node.get_closest_marker(name) or node.iter_markers(name).
Docs: https://docs.pytest.org/en/latest/mark.html#updating-code
kwargs = ['{name}={value}'.format(name=key, value=represent(marker.kwargs[key])) for key in marker.kwargs]
/lib/python2.7/site-packages/allure_pytest/utils.py:80: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly.
Please use node.get_closest_marker(name) or node.iter_markers(name).
Docs: https://docs.pytest.org/en/latest/mark.html#updating-code
return '@pytest.mark.{name}'.format(name=marker.name)
Activity
dstoianov commentedon Oct 23, 2018
same error
sseliverstov commentedon Oct 29, 2018
fixed in 2.5.3
deepjia commentedon Oct 31, 2018
Still got two warnings with allure-pytest-2.5.3 & pytest-3.8.2/pytest-3.9.3:
tsbxmw commentedon Nov 13, 2018
https://github.com/allure-framework/allure2/issues/862
bug fix of issue allure-framework#300 : RemovedInPytest4Warning
remove pytest warning (fixes allure-framework#300 via allure-framewor…
remove pytest warning (fixes allure-framework#300 via allure-framewor…
remove pytest warning (fixes allure-framework#300 via allure-framewor…
remove pytest warning (fixes allure-framework#300 via allure-framewor…