2016-12-20 20:36:57 +08:00
|
|
|
import re
|
2018-10-25 15:01:29 +08:00
|
|
|
import warnings
|
2019-12-03 20:34:41 +08:00
|
|
|
from typing import Optional
|
2017-05-30 05:59:34 +08:00
|
|
|
|
2015-07-29 07:01:11 +08:00
|
|
|
import pytest
|
2020-11-09 12:23:31 +08:00
|
|
|
from _pytest.pytester import Pytester
|
2015-08-05 06:27:13 +08:00
|
|
|
from _pytest.recwarn import WarningsRecorder
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2009-09-06 22:59:39 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_recwarn_stacklevel(recwarn: WarningsRecorder) -> None:
|
2018-10-18 10:36:41 +08:00
|
|
|
warnings.warn("hello")
|
|
|
|
warn = recwarn.pop()
|
|
|
|
assert warn.filename == __file__
|
|
|
|
|
|
|
|
|
2020-11-09 12:23:31 +08:00
|
|
|
def test_recwarn_functional(pytester: Pytester) -> None:
|
|
|
|
pytester.makepyfile(
|
2018-05-23 22:48:46 +08:00
|
|
|
"""
|
2009-09-06 22:59:39 +08:00
|
|
|
import warnings
|
|
|
|
def test_method(recwarn):
|
|
|
|
warnings.warn("hello")
|
|
|
|
warn = recwarn.pop()
|
|
|
|
assert isinstance(warn.message, UserWarning)
|
2018-05-23 22:48:46 +08:00
|
|
|
"""
|
|
|
|
)
|
2020-11-09 12:23:31 +08:00
|
|
|
reprec = pytester.inline_run()
|
2018-09-05 04:02:56 +08:00
|
|
|
reprec.assertoutcome(passed=1)
|
2010-07-27 03:15:15 +08:00
|
|
|
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2021-06-12 22:38:24 +08:00
|
|
|
@pytest.mark.filterwarnings("")
|
|
|
|
def test_recwarn_captures_deprecation_warning(recwarn: WarningsRecorder) -> None:
|
|
|
|
"""
|
|
|
|
Check that recwarn can capture DeprecationWarning by default
|
|
|
|
without custom filterwarnings (see #8666).
|
|
|
|
"""
|
|
|
|
warnings.warn(DeprecationWarning("some deprecation"))
|
|
|
|
assert len(recwarn) == 1
|
|
|
|
assert recwarn.pop(DeprecationWarning)
|
|
|
|
|
|
|
|
|
2019-06-03 06:32:00 +08:00
|
|
|
class TestWarningsRecorderChecker:
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_recording(self) -> None:
|
2020-09-28 03:20:31 +08:00
|
|
|
rec = WarningsRecorder(_ispytest=True)
|
2015-07-29 07:01:11 +08:00
|
|
|
with rec:
|
|
|
|
assert not rec.list
|
2017-12-27 11:47:26 +08:00
|
|
|
warnings.warn_explicit("hello", UserWarning, "xyz", 13)
|
2015-07-29 07:01:11 +08:00
|
|
|
assert len(rec.list) == 1
|
2017-12-27 11:47:26 +08:00
|
|
|
warnings.warn(DeprecationWarning("hello"))
|
2015-07-29 07:01:11 +08:00
|
|
|
assert len(rec.list) == 2
|
|
|
|
warn = rec.pop()
|
|
|
|
assert str(warn.message) == "hello"
|
2017-11-04 23:17:20 +08:00
|
|
|
values = rec.list
|
2015-07-29 07:01:11 +08:00
|
|
|
rec.clear()
|
|
|
|
assert len(rec.list) == 0
|
2017-11-04 23:17:20 +08:00
|
|
|
assert values is rec.list
|
2018-11-23 02:05:10 +08:00
|
|
|
pytest.raises(AssertionError, rec.pop)
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_warn_stacklevel(self) -> None:
|
2019-04-27 22:25:37 +08:00
|
|
|
"""#4243"""
|
2020-09-28 03:20:31 +08:00
|
|
|
rec = WarningsRecorder(_ispytest=True)
|
2018-10-26 15:01:25 +08:00
|
|
|
with rec:
|
|
|
|
warnings.warn("test", DeprecationWarning, 2)
|
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_typechecking(self) -> None:
|
2015-08-05 06:27:13 +08:00
|
|
|
from _pytest.recwarn import WarningsChecker
|
2018-05-23 22:48:46 +08:00
|
|
|
|
2015-07-29 07:01:11 +08:00
|
|
|
with pytest.raises(TypeError):
|
2020-09-28 03:20:31 +08:00
|
|
|
WarningsChecker(5, _ispytest=True) # type: ignore[arg-type]
|
2015-07-29 07:01:11 +08:00
|
|
|
with pytest.raises(TypeError):
|
2020-09-28 03:20:31 +08:00
|
|
|
WarningsChecker(("hi", RuntimeWarning), _ispytest=True) # type: ignore[arg-type]
|
2015-07-29 07:01:11 +08:00
|
|
|
with pytest.raises(TypeError):
|
2020-09-28 03:20:31 +08:00
|
|
|
WarningsChecker([DeprecationWarning, RuntimeWarning], _ispytest=True) # type: ignore[arg-type]
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_invalid_enter_exit(self) -> None:
|
2015-07-29 07:01:11 +08:00
|
|
|
# wrap this test in WarningsRecorder to ensure warning state gets reset
|
2020-09-28 03:20:31 +08:00
|
|
|
with WarningsRecorder(_ispytest=True):
|
2015-07-29 07:01:11 +08:00
|
|
|
with pytest.raises(RuntimeError):
|
2020-09-28 03:20:31 +08:00
|
|
|
rec = WarningsRecorder(_ispytest=True)
|
2015-07-29 07:01:11 +08:00
|
|
|
rec.__exit__(None, None, None) # can't exit before entering
|
|
|
|
|
|
|
|
with pytest.raises(RuntimeError):
|
2020-09-28 03:20:31 +08:00
|
|
|
rec = WarningsRecorder(_ispytest=True)
|
2015-07-29 07:01:11 +08:00
|
|
|
with rec:
|
|
|
|
with rec:
|
|
|
|
pass # can't enter twice
|
|
|
|
|
2009-09-06 22:59:39 +08:00
|
|
|
|
2019-06-03 06:32:00 +08:00
|
|
|
class TestDeprecatedCall:
|
2015-11-27 02:27:20 +08:00
|
|
|
"""test pytest.deprecated_call()"""
|
2009-09-06 22:59:39 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def dep(self, i: int, j: Optional[int] = None) -> int:
|
2015-11-27 02:27:20 +08:00
|
|
|
if i == 0:
|
2018-05-23 22:48:46 +08:00
|
|
|
warnings.warn("is deprecated", DeprecationWarning, stacklevel=1)
|
2015-11-27 02:27:20 +08:00
|
|
|
return 42
|
2009-09-06 22:59:39 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def dep_explicit(self, i: int) -> None:
|
2015-11-27 02:27:20 +08:00
|
|
|
if i == 0:
|
2018-05-23 22:48:46 +08:00
|
|
|
warnings.warn_explicit(
|
|
|
|
"dep_explicit", category=DeprecationWarning, filename="hello", lineno=3
|
|
|
|
)
|
2015-09-21 21:18:29 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_call_raises(self) -> None:
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception, match="No warnings of type"):
|
2015-12-09 08:40:05 +08:00
|
|
|
pytest.deprecated_call(self.dep, 3, 5)
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_call(self) -> None:
|
2015-12-09 08:40:05 +08:00
|
|
|
pytest.deprecated_call(self.dep, 0, 5)
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_call_ret(self) -> None:
|
2015-11-27 02:27:20 +08:00
|
|
|
ret = pytest.deprecated_call(self.dep, 0)
|
2015-07-29 07:01:11 +08:00
|
|
|
assert ret == 42
|
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_call_preserves(self) -> None:
|
|
|
|
# Type ignored because `onceregistry` and `filters` are not
|
|
|
|
# documented API.
|
|
|
|
onceregistry = warnings.onceregistry.copy() # type: ignore
|
|
|
|
filters = warnings.filters[:] # type: ignore
|
2017-12-27 11:47:26 +08:00
|
|
|
warn = warnings.warn
|
|
|
|
warn_explicit = warnings.warn_explicit
|
2015-07-29 07:01:11 +08:00
|
|
|
self.test_deprecated_call_raises()
|
|
|
|
self.test_deprecated_call()
|
2019-12-03 20:34:41 +08:00
|
|
|
assert onceregistry == warnings.onceregistry # type: ignore
|
|
|
|
assert filters == warnings.filters # type: ignore
|
2017-12-27 11:47:26 +08:00
|
|
|
assert warn is warnings.warn
|
|
|
|
assert warn_explicit is warnings.warn_explicit
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_explicit_call_raises(self) -> None:
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception):
|
2015-11-27 02:27:20 +08:00
|
|
|
pytest.deprecated_call(self.dep_explicit, 3)
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_explicit_call(self) -> None:
|
2015-11-27 02:27:20 +08:00
|
|
|
pytest.deprecated_call(self.dep_explicit, 0)
|
|
|
|
pytest.deprecated_call(self.dep_explicit, 0)
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2018-05-23 22:48:46 +08:00
|
|
|
@pytest.mark.parametrize("mode", ["context_manager", "call"])
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_call_no_warning(self, mode) -> None:
|
2017-06-07 09:25:15 +08:00
|
|
|
"""Ensure deprecated_call() raises the expected failure when its block/function does
|
|
|
|
not raise a deprecation warning.
|
|
|
|
"""
|
2018-05-23 22:48:46 +08:00
|
|
|
|
2017-06-07 09:25:15 +08:00
|
|
|
def f():
|
|
|
|
pass
|
|
|
|
|
2018-10-10 23:00:59 +08:00
|
|
|
msg = "No warnings of type (.*DeprecationWarning.*, .*PendingDeprecationWarning.*)"
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception, match=msg):
|
2018-05-23 22:48:46 +08:00
|
|
|
if mode == "call":
|
2017-06-07 09:25:15 +08:00
|
|
|
pytest.deprecated_call(f)
|
|
|
|
else:
|
|
|
|
with pytest.deprecated_call():
|
|
|
|
f()
|
2015-09-21 21:18:29 +08:00
|
|
|
|
2018-05-23 22:48:46 +08:00
|
|
|
@pytest.mark.parametrize(
|
|
|
|
"warning_type", [PendingDeprecationWarning, DeprecationWarning]
|
|
|
|
)
|
|
|
|
@pytest.mark.parametrize("mode", ["context_manager", "call"])
|
|
|
|
@pytest.mark.parametrize("call_f_first", [True, False])
|
|
|
|
@pytest.mark.filterwarnings("ignore")
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_call_modes(self, warning_type, mode, call_f_first) -> None:
|
2017-06-07 09:25:15 +08:00
|
|
|
"""Ensure deprecated_call() captures a deprecation warning as expected inside its
|
|
|
|
block/function.
|
|
|
|
"""
|
2018-05-23 22:48:46 +08:00
|
|
|
|
2015-11-27 02:27:20 +08:00
|
|
|
def f():
|
2017-05-30 09:46:15 +08:00
|
|
|
warnings.warn(warning_type("hi"))
|
2017-06-07 09:25:15 +08:00
|
|
|
return 10
|
|
|
|
|
|
|
|
# ensure deprecated_call() can capture the warning even if it has already been triggered
|
|
|
|
if call_f_first:
|
|
|
|
assert f() == 10
|
2018-05-23 22:48:46 +08:00
|
|
|
if mode == "call":
|
2017-06-07 09:25:15 +08:00
|
|
|
assert pytest.deprecated_call(f) == 10
|
2017-05-30 09:46:15 +08:00
|
|
|
else:
|
|
|
|
with pytest.deprecated_call():
|
2017-06-07 09:25:15 +08:00
|
|
|
assert f() == 10
|
|
|
|
|
2018-05-23 22:48:46 +08:00
|
|
|
@pytest.mark.parametrize("mode", ["context_manager", "call"])
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_call_exception_is_raised(self, mode) -> None:
|
2017-06-07 09:25:15 +08:00
|
|
|
"""If the block of the code being tested by deprecated_call() raises an exception,
|
|
|
|
it must raise the exception undisturbed.
|
|
|
|
"""
|
2018-05-23 22:48:46 +08:00
|
|
|
|
2017-06-07 09:25:15 +08:00
|
|
|
def f():
|
2018-05-23 22:48:46 +08:00
|
|
|
raise ValueError("some exception")
|
2017-06-07 09:25:15 +08:00
|
|
|
|
2018-05-23 22:48:46 +08:00
|
|
|
with pytest.raises(ValueError, match="some exception"):
|
|
|
|
if mode == "call":
|
2017-06-07 09:25:15 +08:00
|
|
|
pytest.deprecated_call(f)
|
|
|
|
else:
|
|
|
|
with pytest.deprecated_call():
|
|
|
|
f()
|
2015-09-29 00:09:44 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_call_specificity(self) -> None:
|
2018-05-23 22:48:46 +08:00
|
|
|
other_warnings = [
|
|
|
|
Warning,
|
|
|
|
UserWarning,
|
|
|
|
SyntaxWarning,
|
|
|
|
RuntimeWarning,
|
|
|
|
FutureWarning,
|
|
|
|
ImportWarning,
|
|
|
|
UnicodeWarning,
|
|
|
|
]
|
2015-09-29 00:24:20 +08:00
|
|
|
for warning in other_warnings:
|
2018-05-23 22:48:46 +08:00
|
|
|
|
2015-11-27 02:27:20 +08:00
|
|
|
def f():
|
2017-06-07 09:25:15 +08:00
|
|
|
warnings.warn(warning("hi"))
|
|
|
|
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception):
|
2015-09-29 00:24:20 +08:00
|
|
|
pytest.deprecated_call(f)
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception):
|
2017-06-07 09:25:15 +08:00
|
|
|
with pytest.deprecated_call():
|
|
|
|
f()
|
2015-09-29 00:24:20 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_deprecated_call_supports_match(self) -> None:
|
2018-10-10 23:00:59 +08:00
|
|
|
with pytest.deprecated_call(match=r"must be \d+$"):
|
|
|
|
warnings.warn("value must be 42", DeprecationWarning)
|
|
|
|
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception):
|
2018-10-10 23:00:59 +08:00
|
|
|
with pytest.deprecated_call(match=r"must be \d+$"):
|
|
|
|
warnings.warn("this is not here", DeprecationWarning)
|
|
|
|
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-06-03 06:32:00 +08:00
|
|
|
class TestWarns:
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_check_callable(self) -> None:
|
2019-06-30 22:40:24 +08:00
|
|
|
source = "warnings.warn('w1', RuntimeWarning)"
|
|
|
|
with pytest.raises(TypeError, match=r".* must be callable"):
|
2019-12-03 20:34:41 +08:00
|
|
|
pytest.warns(RuntimeWarning, source) # type: ignore
|
2019-06-30 22:40:24 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_several_messages(self) -> None:
|
2015-07-29 07:01:11 +08:00
|
|
|
# different messages, b/c Python suppresses multiple identical warnings
|
2019-06-30 22:40:24 +08:00
|
|
|
pytest.warns(RuntimeWarning, lambda: warnings.warn("w1", RuntimeWarning))
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception):
|
2019-06-30 22:40:24 +08:00
|
|
|
pytest.warns(UserWarning, lambda: warnings.warn("w2", RuntimeWarning))
|
|
|
|
pytest.warns(RuntimeWarning, lambda: warnings.warn("w3", RuntimeWarning))
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_function(self) -> None:
|
2018-05-23 22:48:46 +08:00
|
|
|
pytest.warns(
|
|
|
|
SyntaxWarning, lambda msg: warnings.warn(msg, SyntaxWarning), "syntax"
|
|
|
|
)
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_warning_tuple(self) -> None:
|
2018-05-23 22:48:46 +08:00
|
|
|
pytest.warns(
|
|
|
|
(RuntimeWarning, SyntaxWarning), lambda: warnings.warn("w1", RuntimeWarning)
|
|
|
|
)
|
|
|
|
pytest.warns(
|
|
|
|
(RuntimeWarning, SyntaxWarning), lambda: warnings.warn("w2", SyntaxWarning)
|
|
|
|
)
|
|
|
|
pytest.raises(
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
pytest.fail.Exception,
|
2018-05-23 22:48:46 +08:00
|
|
|
lambda: pytest.warns(
|
|
|
|
(RuntimeWarning, SyntaxWarning),
|
|
|
|
lambda: warnings.warn("w3", UserWarning),
|
|
|
|
),
|
|
|
|
)
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_as_contextmanager(self) -> None:
|
2015-07-29 07:01:11 +08:00
|
|
|
with pytest.warns(RuntimeWarning):
|
|
|
|
warnings.warn("runtime", RuntimeWarning)
|
|
|
|
|
2016-12-20 20:36:57 +08:00
|
|
|
with pytest.warns(UserWarning):
|
|
|
|
warnings.warn("user", UserWarning)
|
|
|
|
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception) as excinfo:
|
2015-07-29 07:01:11 +08:00
|
|
|
with pytest.warns(RuntimeWarning):
|
|
|
|
warnings.warn("user", UserWarning)
|
2018-05-23 22:48:46 +08:00
|
|
|
excinfo.match(
|
|
|
|
r"DID NOT WARN. No warnings of type \(.+RuntimeWarning.+,\) was emitted. "
|
|
|
|
r"The list of emitted warnings is: \[UserWarning\('user',?\)\]."
|
|
|
|
)
|
2015-07-29 07:01:11 +08:00
|
|
|
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception) as excinfo:
|
2015-07-29 07:01:11 +08:00
|
|
|
with pytest.warns(UserWarning):
|
|
|
|
warnings.warn("runtime", RuntimeWarning)
|
2018-05-23 22:48:46 +08:00
|
|
|
excinfo.match(
|
|
|
|
r"DID NOT WARN. No warnings of type \(.+UserWarning.+,\) was emitted. "
|
|
|
|
r"The list of emitted warnings is: \[RuntimeWarning\('runtime',?\)\]."
|
|
|
|
)
|
2016-12-20 20:36:57 +08:00
|
|
|
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception) as excinfo:
|
2016-12-20 20:36:57 +08:00
|
|
|
with pytest.warns(UserWarning):
|
|
|
|
pass
|
2018-05-23 22:48:46 +08:00
|
|
|
excinfo.match(
|
|
|
|
r"DID NOT WARN. No warnings of type \(.+UserWarning.+,\) was emitted. "
|
|
|
|
r"The list of emitted warnings is: \[\]."
|
|
|
|
)
|
2016-12-20 20:36:57 +08:00
|
|
|
|
|
|
|
warning_classes = (UserWarning, FutureWarning)
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception) as excinfo:
|
2016-12-20 20:36:57 +08:00
|
|
|
with pytest.warns(warning_classes) as warninfo:
|
|
|
|
warnings.warn("runtime", RuntimeWarning)
|
|
|
|
warnings.warn("import", ImportWarning)
|
|
|
|
|
2018-05-23 22:48:46 +08:00
|
|
|
message_template = (
|
|
|
|
"DID NOT WARN. No warnings of type {0} was emitted. "
|
|
|
|
"The list of emitted warnings is: {1}."
|
|
|
|
)
|
|
|
|
excinfo.match(
|
|
|
|
re.escape(
|
|
|
|
message_template.format(
|
|
|
|
warning_classes, [each.message for each in warninfo]
|
|
|
|
)
|
|
|
|
)
|
|
|
|
)
|
2015-07-29 07:01:11 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_record(self) -> None:
|
2015-07-29 07:01:11 +08:00
|
|
|
with pytest.warns(UserWarning) as record:
|
|
|
|
warnings.warn("user", UserWarning)
|
|
|
|
|
|
|
|
assert len(record) == 1
|
|
|
|
assert str(record[0].message) == "user"
|
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_record_only(self) -> None:
|
2021-05-15 22:15:43 +08:00
|
|
|
with pytest.warns() as record:
|
2015-07-29 07:01:11 +08:00
|
|
|
warnings.warn("user", UserWarning)
|
|
|
|
warnings.warn("runtime", RuntimeWarning)
|
2009-09-06 22:59:39 +08:00
|
|
|
|
2015-07-29 07:01:11 +08:00
|
|
|
assert len(record) == 2
|
|
|
|
assert str(record[0].message) == "user"
|
|
|
|
assert str(record[1].message) == "runtime"
|
2021-05-15 22:15:43 +08:00
|
|
|
|
|
|
|
def test_record_only_none_deprecated_warn(self) -> None:
|
2021-07-04 16:27:43 +08:00
|
|
|
# This should become an error when WARNS_NONE_ARG is removed in Pytest 8.0
|
2021-05-15 22:15:43 +08:00
|
|
|
with warnings.catch_warnings():
|
|
|
|
warnings.simplefilter("ignore")
|
2021-05-17 16:50:59 +08:00
|
|
|
with pytest.warns(None) as record: # type: ignore[call-overload]
|
2021-05-15 22:15:43 +08:00
|
|
|
warnings.warn("user", UserWarning)
|
|
|
|
warnings.warn("runtime", RuntimeWarning)
|
|
|
|
|
|
|
|
assert len(record) == 2
|
|
|
|
assert str(record[0].message) == "user"
|
|
|
|
assert str(record[1].message) == "runtime"
|
2015-08-07 03:05:01 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_record_by_subclass(self) -> None:
|
2016-12-20 21:57:48 +08:00
|
|
|
with pytest.warns(Warning) as record:
|
|
|
|
warnings.warn("user", UserWarning)
|
|
|
|
warnings.warn("runtime", RuntimeWarning)
|
|
|
|
|
|
|
|
assert len(record) == 2
|
|
|
|
assert str(record[0].message) == "user"
|
|
|
|
assert str(record[1].message) == "runtime"
|
|
|
|
|
2017-07-17 07:25:10 +08:00
|
|
|
class MyUserWarning(UserWarning):
|
|
|
|
pass
|
2016-12-29 17:18:33 +08:00
|
|
|
|
2017-07-17 07:25:10 +08:00
|
|
|
class MyRuntimeWarning(RuntimeWarning):
|
|
|
|
pass
|
2016-12-29 16:34:21 +08:00
|
|
|
|
|
|
|
with pytest.warns((UserWarning, RuntimeWarning)) as record:
|
|
|
|
warnings.warn("user", MyUserWarning)
|
|
|
|
warnings.warn("runtime", MyRuntimeWarning)
|
|
|
|
|
|
|
|
assert len(record) == 2
|
|
|
|
assert str(record[0].message) == "user"
|
|
|
|
assert str(record[1].message) == "runtime"
|
|
|
|
|
2020-11-09 12:23:31 +08:00
|
|
|
def test_double_test(self, pytester: Pytester) -> None:
|
2015-08-07 03:05:01 +08:00
|
|
|
"""If a test is run again, the warning should still be raised"""
|
2020-11-09 12:23:31 +08:00
|
|
|
pytester.makepyfile(
|
2018-05-23 22:48:46 +08:00
|
|
|
"""
|
2015-08-07 09:30:01 +08:00
|
|
|
import pytest
|
|
|
|
import warnings
|
|
|
|
|
|
|
|
@pytest.mark.parametrize('run', [1, 2])
|
|
|
|
def test(run):
|
|
|
|
with pytest.warns(RuntimeWarning):
|
|
|
|
warnings.warn("runtime", RuntimeWarning)
|
2018-05-23 22:48:46 +08:00
|
|
|
"""
|
|
|
|
)
|
2020-11-09 12:23:31 +08:00
|
|
|
result = pytester.runpytest()
|
2018-05-23 22:48:46 +08:00
|
|
|
result.stdout.fnmatch_lines(["*2 passed in*"])
|
2017-08-22 19:48:29 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_match_regex(self) -> None:
|
2018-05-23 22:48:46 +08:00
|
|
|
with pytest.warns(UserWarning, match=r"must be \d+$"):
|
2017-08-22 19:48:29 +08:00
|
|
|
warnings.warn("value must be 42", UserWarning)
|
|
|
|
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception):
|
2018-05-23 22:48:46 +08:00
|
|
|
with pytest.warns(UserWarning, match=r"must be \d+$"):
|
2017-08-22 19:48:29 +08:00
|
|
|
warnings.warn("this is not here", UserWarning)
|
|
|
|
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception):
|
2018-05-23 22:48:46 +08:00
|
|
|
with pytest.warns(FutureWarning, match=r"must be \d+$"):
|
2017-09-06 07:13:08 +08:00
|
|
|
warnings.warn("value must be 42", UserWarning)
|
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_one_from_multiple_warns(self) -> None:
|
2018-05-23 22:48:46 +08:00
|
|
|
with pytest.warns(UserWarning, match=r"aaa"):
|
2017-08-22 19:48:29 +08:00
|
|
|
warnings.warn("cccccccccc", UserWarning)
|
|
|
|
warnings.warn("bbbbbbbbbb", UserWarning)
|
|
|
|
warnings.warn("aaaaaaaaaa", UserWarning)
|
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_none_of_multiple_warns(self) -> None:
|
Use a hack to make typing of pytest.fail.Exception & co work
Mypy currently is unable to handle assigning attributes on function:
https://github.com/python/mypy/issues/2087.
pytest uses this for the outcome exceptions -- `pytest.fail.Exception`,
`pytest.exit.Exception` etc, and this is the canonical name by which they
are referred.
Initially we started working around this with type: ignores, and later
by switching e.g. `pytest.fail.Exception` with the direct exception
`Failed`. But this causes a lot of churn and is not as nice. And I also
found that some code relies on it, in skipping.py:
def pytest_configure(config):
if config.option.runxfail:
# yay a hack
import pytest
old = pytest.xfail
config._cleanup.append(lambda: setattr(pytest, "xfail", old))
def nop(*args, **kwargs):
pass
nop.Exception = xfail.Exception
setattr(pytest, "xfail", nop)
...
So it seems better to support it. Use a hack to make it work. The rest
of the commit rolls back all of the workarounds we added up to now.
`pytest.raises.Exception` also exists, but it's not used much so I kept
it as-is for now.
Hopefully in the future mypy supports this and this ugliness can be
removed.
2020-02-17 03:46:11 +08:00
|
|
|
with pytest.raises(pytest.fail.Exception):
|
2018-05-23 22:48:46 +08:00
|
|
|
with pytest.warns(UserWarning, match=r"aaa"):
|
2017-08-22 19:48:29 +08:00
|
|
|
warnings.warn("bbbbbbbbbb", UserWarning)
|
|
|
|
warnings.warn("cccccccccc", UserWarning)
|
2018-10-11 00:36:19 +08:00
|
|
|
|
|
|
|
@pytest.mark.filterwarnings("ignore")
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_can_capture_previously_warned(self) -> None:
|
2020-06-25 19:08:47 +08:00
|
|
|
def f() -> int:
|
2018-10-11 00:36:19 +08:00
|
|
|
warnings.warn(UserWarning("ohai"))
|
|
|
|
return 10
|
|
|
|
|
|
|
|
assert f() == 10
|
|
|
|
assert pytest.warns(UserWarning, f) == 10
|
|
|
|
assert pytest.warns(UserWarning, f) == 10
|
2020-06-25 19:08:47 +08:00
|
|
|
assert pytest.warns(UserWarning, f) != "10" # type: ignore[comparison-overlap]
|
2019-07-14 16:39:30 +08:00
|
|
|
|
2019-12-03 20:34:41 +08:00
|
|
|
def test_warns_context_manager_with_kwargs(self) -> None:
|
2019-07-14 16:39:30 +08:00
|
|
|
with pytest.raises(TypeError) as excinfo:
|
2019-12-03 20:34:41 +08:00
|
|
|
with pytest.warns(UserWarning, foo="bar"): # type: ignore
|
2019-07-14 16:39:30 +08:00
|
|
|
pass
|
|
|
|
assert "Unexpected keyword arguments" in str(excinfo.value)
|