diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2021-05-30 17:39:20 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2021-05-30 18:03:05 -0400 |
| commit | 30c023b5b74f9c798645cbb3f35362ae046a4c25 (patch) | |
| tree | e86df1a4c044ec9b2919068297dfd91a382eeb84 /tests/test_summary.py | |
| parent | 22fe2eb167a18dda8fd3e14cbf9166a1c7331fb9 (diff) | |
| download | python-coveragepy-git-30c023b5b74f9c798645cbb3f35362ae046a4c25.tar.gz | |
feat: warnings are now real warnings
This makes coverage warnings visible when running test suites under
pytest. But it also means some uninteresting warnings would show up in
our own test suite, so we had to catch or suppress those.
Diffstat (limited to 'tests/test_summary.py')
| -rw-r--r-- | tests/test_summary.py | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/tests/test_summary.py b/tests/test_summary.py index a6384c46..b71921c7 100644 --- a/tests/test_summary.py +++ b/tests/test_summary.py @@ -595,12 +595,13 @@ class SummaryTest(UsingModulesMixin, CoverageTest): self.make_file("mycode.py", "This isn't python at all!") report = self.report_from_command("coverage report -i mycode.py") - # Coverage.py warning: Couldn't parse Python file blah_blah/mycode.py (couldnt-parse) + # CoverageWarning: Couldn't parse Python file blah_blah/mycode.py (couldnt-parse) + # (source line) # Name Stmts Miss Cover # ---------------------------- # No data to report. - assert self.line_count(report) == 4 + assert self.line_count(report) == 5 assert 'No data to report.' in report assert '(couldnt-parse)' in report |