You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The HTML report now shows separate coverage totals for statements and
branches, as well as the usual combined coverage percentage. Thanks to Ryuta
Otsuka for the discussion <issue 2081_>_ and the implementation <pull 2085_>_.
The JSON report now includes separate coverage totals for statements and
branches, thanks to Ryuta Otsuka <pull 2090_>_.
Fix: except* clauses were not handled properly under the "sysmon"
measurement core, causing KeyError exceptions as described in issue 2086_.
This is now fixed.
Fix: we now defend against aggressive mocking of open() that could cause
errors inside coverage.py. An example of a failure is in issue 2083_.
Fix: in unusual cases where a test suite intentionally exhausts the system's
file descriptors to test handling errors in open(), coverage.py would
fail when trying to open source files, as described in issue 2091_. This
is now fixed.
A small tweak to the HTML report: file paths now use thin spaces around
slashes to make them easier to read.
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%
✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (f4edcc4) to head (474672b). ⚠️ Report is 1 commits behind head on master.
❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
renovatebot
changed the title
chore(deps): update dependency coverage to v7.12.0
chore(deps): update dependency coverage to v7.12.0 - autoclosed
Nov 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.11.3->7.12.0Release Notes
coveragepy/coveragepy (coverage)
v7.12.0Compare Source
The HTML report now shows separate coverage totals for statements and
branches, as well as the usual combined coverage percentage. Thanks to Ryuta
Otsuka for the
discussion <issue 2081_>_ and theimplementation <pull 2085_>_.The JSON report now includes separate coverage totals for statements and
branches, thanks to
Ryuta Otsuka <pull 2090_>_.Fix:
except*clauses were not handled properly under the "sysmon"measurement core, causing KeyError exceptions as described in
issue 2086_.This is now fixed.
Fix: we now defend against aggressive mocking of
open()that could causeerrors inside coverage.py. An example of a failure is in
issue 2083_.Fix: in unusual cases where a test suite intentionally exhausts the system's
file descriptors to test handling errors in
open(), coverage.py wouldfail when trying to open source files, as described in
issue 2091_. Thisis now fixed.
A small tweak to the HTML report: file paths now use thin spaces around
slashes to make them easier to read.
.. _issue 2081: #2081
.. _issue 2083: #2083
.. _pull 2085: #2085
.. _issue 2086: #2086
.. _pull 2090: #2090
.. _issue 2091: #2091
.. _changes_7-11-3:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.