jiuyuan
/
test_ok1
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
test_ok1/testing/test_warnings.py

61 lines
2.0 KiB
Python
Raw Normal View History

Add tests and integrated the original code into the core
2016-11-21 18:26:43 +08:00
import pytest
@pytest.fixture
def pyfile_with_warnings(testdir):
testdir.makepyfile('''
import warnings
def test_func():
warnings.warn(PendingDeprecationWarning("functionality is pending deprecation"))
warnings.warn(DeprecationWarning("functionality is deprecated"))
''')
def test_normal_flow(testdir, pyfile_with_warnings):
Use warnings.catch_warnings instead of WarningsRecorder This has the benefical side-effect of not calling the original warnings.showwarnings function, which in its original form only writes the formatted warning to sys.stdout. Calling the original warnings.showwarnings has the effect that nested WarningsRecorder all catch the warnings: with WarningsRecorder() as rec1: with WarningsRecorder() as rec2: warnings.warn(UserWarning, 'some warning') (both rec1 and rec2 sees the warning) When running tests with `testdir`, the main pytest session would then see the warnings created by the internal code being tested (if any), and the main pytest session would end up with warnings as well.
2017-02-18 22:57:26 +08:00
result = testdir.runpytest()
Add tests and integrated the original code into the core
2016-11-21 18:26:43 +08:00
result.stdout.fnmatch_lines([
'*== pytest-warning summary ==*',
'WW0 in *test_normal_flow.py:1 the following warning was recorded:',
' test_normal_flow.py:3: PendingDeprecationWarning: functionality is pending deprecation',
' warnings.warn(PendingDeprecationWarning("functionality is pending deprecation"))',
'WW0 in *test_normal_flow.py:1 the following warning was recorded:',
' test_normal_flow.py:4: DeprecationWarning: functionality is deprecated',
' warnings.warn(DeprecationWarning("functionality is deprecated"))',
'* 1 passed, 2 pytest-warnings*',
])
@pytest.mark.parametrize('method', ['cmdline', 'ini'])
def test_as_errors(testdir, pyfile_with_warnings, method):
args = ('-W', 'error') if method == 'cmdline' else ()
if method == 'ini':
testdir.makeini('''
[pytest]
filterwarnings= error
''')
Use warnings.catch_warnings instead of WarningsRecorder This has the benefical side-effect of not calling the original warnings.showwarnings function, which in its original form only writes the formatted warning to sys.stdout. Calling the original warnings.showwarnings has the effect that nested WarningsRecorder all catch the warnings: with WarningsRecorder() as rec1: with WarningsRecorder() as rec2: warnings.warn(UserWarning, 'some warning') (both rec1 and rec2 sees the warning) When running tests with `testdir`, the main pytest session would then see the warnings created by the internal code being tested (if any), and the main pytest session would end up with warnings as well.
2017-02-18 22:57:26 +08:00
result = testdir.runpytest(*args)
Add tests and integrated the original code into the core
2016-11-21 18:26:43 +08:00
result.stdout.fnmatch_lines([
'E PendingDeprecationWarning: functionality is pending deprecation',
'test_as_errors.py:3: PendingDeprecationWarning',
'* 1 failed in *',
])
@pytest.mark.parametrize('method', ['cmdline', 'ini'])
def test_ignore(testdir, pyfile_with_warnings, method):
args = ('-W', 'ignore') if method == 'cmdline' else ()
if method == 'ini':
testdir.makeini('''
[pytest]
filterwarnings= ignore
''')
Use warnings.catch_warnings instead of WarningsRecorder This has the benefical side-effect of not calling the original warnings.showwarnings function, which in its original form only writes the formatted warning to sys.stdout. Calling the original warnings.showwarnings has the effect that nested WarningsRecorder all catch the warnings: with WarningsRecorder() as rec1: with WarningsRecorder() as rec2: warnings.warn(UserWarning, 'some warning') (both rec1 and rec2 sees the warning) When running tests with `testdir`, the main pytest session would then see the warnings created by the internal code being tested (if any), and the main pytest session would end up with warnings as well.
2017-02-18 22:57:26 +08:00
result = testdir.runpytest(*args)
Add tests and integrated the original code into the core
2016-11-21 18:26:43 +08:00
result.stdout.fnmatch_lines([
'* 1 passed in *',
])
assert 'pytest-warning summary' not in result.stdout.str()