Update dependency pytest-cov to v7#1767
Open
k1h-renovate[bot] wants to merge 1 commit into
Open
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #1767 +/- ##
=======================================
Coverage 92.98% 92.98%
=======================================
Files 30 30
Lines 5044 5044
=======================================
Hits 4690 4690
Misses 354 354 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
i-oden
added
tests
k1h-renovate
Bot
force-pushed
the
renovate/pytest-cov-7.x
branch
from
9d54ae3 to
1ad4bc7
Compare
k1h-renovate
Bot
force-pushed
the
renovate/pytest-cov-7.x
branch
from
1ad4bc7 to
225ba2e
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
==3.0.0→==7.1.0Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
pytest-dev/pytest-cov (pytest-cov)
v7.1.0Compare Source
Fixed total coverage computation to always be consistent, regardless of reporting settings.
Previously some reports could produce different total counts, and consequently can make --cov-fail-under behave different depending on
reporting options.
See
#​641 <https://github.com/pytest-dev/pytest-cov/issues/641>_.Improve handling of ResourceWarning from sqlite3.
The plugin adds warning filter for sqlite3
ResourceWarningunclosed database (since 6.2.0).It checks if there is already existing plugin for this message by comparing filter regular expression.
When filter is specified on command line the message is escaped and does not match an expected message.
A check for an escaped regular expression is added to handle this case.
With this fix one can suppress
ResourceWarningfrom sqlite3 from command line::pytest -W "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning" ...
Various improvements to documentation.
Contributed by Art Pelling in
#​718 <https://github.com/pytest-dev/pytest-cov/pull/718>_ and"vivodi" in
#​738 <https://github.com/pytest-dev/pytest-cov/pull/738>.Also closed
#​736 <https://github.com/pytest-dev/pytest-cov/issues/736>.Fixed some assertions in tests.
Contributed by in Markéta Machová in
#​722 <https://github.com/pytest-dev/pytest-cov/pull/722>_.Removed unnecessary coverage configuration copying (meant as a backup because reporting commands had configuration side-effects before coverage 5.0).
v7.0.0Compare Source
Dropped support for subprocesses measurement.
It was a feature added long time ago when coverage lacked a nice way to measure subprocesses created in tests.
It relied on a
.pthfile, there was no way to opt-out and it created bad interationswith
coverage's new patch system <https://coverage.readthedocs.io/en/latest/config.html#run-patch>_ addedin
7.10 <https://coverage.readthedocs.io/en/7.10.6/changes.html#version-7-10-0-2025-07-24>_.To migrate to this release you might need to enable the suprocess patch, example for
.coveragerc:.. code-block:: ini
[run]
patch = subprocess
This release also requires at least coverage 7.10.6.
Switched packaging to have metadata completely in
pyproject.tomland usehatchling <https://pypi.org/project/hatchling/>_ forbuilding.
Contributed by Ofek Lev in
#​551 <https://github.com/pytest-dev/pytest-cov/pull/551>_with some extras in
#​716 <https://github.com/pytest-dev/pytest-cov/pull/716>_.Removed some not really necessary testing deps like
six.v6.3.0Compare Source
Contributed by Marcos Boger in
#​712 <https://github.com/pytest-dev/pytest-cov/pull/712>_and
#​714 <https://github.com/pytest-dev/pytest-cov/pull/714>_.Anonymous contribution in
#​706 <https://github.com/pytest-dev/pytest-cov/pull/706>_.v6.2.1Compare Source
Added a version requirement for pytest's pluggy dependency (1.2.0, released 2023-06-21) that has the required new-style hookwrapper API.
Removed deprecated license classifier (packaging).
Disabled coverage warnings in two more situations where they have no value:
v6.2.0Compare Source
The plugin now adds 3 rules in the filter warnings configuration to prevent common coverage warnings being raised as obscure errors::
default:unclosed database in <sqlite3.Connection object at:ResourceWarning
once::PytestCovWarning
once::CoverageWarning
This fixes most of the bad interactions that are occurring on pytest 8.4 with
filterwarnings=error.The plugin will check if there already matching rules for the 3 categories
(
ResourceWarning,PytestCovWarning,CoverageWarning) and message (unclosed database in <sqlite3.Connection object at) before adding the filters.This means you can have this in your pytest configuration for complete oblivion (not recommended, if that is not clear)::
filterwarnings = [
"error",
"ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning",
"ignore::PytestCovWarning",
"ignore::CoverageWarning",
]
v6.1.1Compare Source
--cov-contextand theno_covermarker are used together.v6.1.0Compare Source
Contributed by Tsvika Shapira in
#​678 <https://github.com/pytest-dev/pytest-cov/pull/678>_.#​675 <https://github.com/pytest-dev/pytest-cov/issues/675>_.--cov-precision.v6.0.0Compare Source
Now it will perform the check just like
coverage reportwould.--cov-precisioncli option that can override the value set in your coverage configuration.v5.0.0Compare Source
Contributed by Matthias Reichenbach in
#​623 <https://github.com/pytest-dev/pytest-cov/pull/623>_.Contributed by Christian Clauss and Hugo van Kemenade in
#​630 <https://github.com/pytest-dev/pytest-cov/pull/630>,#​631 <https://github.com/pytest-dev/pytest-cov/pull/631>,#​632 <https://github.com/pytest-dev/pytest-cov/pull/632>_ and#​633 <https://github.com/pytest-dev/pytest-cov/pull/633>_.pyproject.tomlexample in the docs.Contributed by Dawn James in
#​626 <https://github.com/pytest-dev/pytest-cov/pull/626>_.Christian Clauss in
#​584 <https://github.com/pytest-dev/pytest-cov/pull/584>_.v4.1.0Compare Source
Contributed by Sorin Sbarnea in
#​558 <https://github.com/pytest-dev/pytest-cov/pull/558>_.when
--cov-report=''is used without--cov-fail-under).Contributed by Jonathan Stewmon in
#​589 <https://github.com/pytest-dev/pytest-cov/pull/589>_.Contributed by Matthew Gamble in
#​582 <https://github.com/pytest-dev/pytest-cov/pull/582>_.Contributed by Mark Mayo in
#​572 <https://github.com/pytest-dev/pytest-cov/pull/572>_.Contributed by a bunch of people in
#​565 <https://github.com/pytest-dev/pytest-cov/pull/565>_.v4.0.0Compare Source
Note that this release drops support for multiprocessing.
--cov-fail-underno longer causespytest --collect-onlyto failContributed by Zac Hatfield-Dodds in
#​511 <https://github.com/pytest-dev/pytest-cov/pull/511>_.Dropped support for multiprocessing (mostly because
issue 82408 <https://github.com/python/cpython/issues/82408>_). This feature wasmostly working but very broken in certain scenarios and made the test suite very flaky and slow.
There is builtin multiprocessing support in coverage and you can migrate to that. All you need is this in your
.coveragerc::[run]
concurrency = multiprocessing
parallel = true
sigterm = true
Fixed deprecation in
setup.pyby trying to import setuptools before distutils.Contributed by Ben Greiner in
#​545 <https://github.com/pytest-dev/pytest-cov/pull/545>_.Removed undesirable new lines that were displayed while reporting was disabled.
Contributed by Delgan in
#​540 <https://github.com/pytest-dev/pytest-cov/pull/540>_.Documentation fixes.
Contributed by Andre Brisco in
#​543 <https://github.com/pytest-dev/pytest-cov/pull/543>_and Colin O'Dell in
#​525 <https://github.com/pytest-dev/pytest-cov/pull/525>_.Added support for LCOV output format via
--cov-report=lcov. Only works with coverage 6.3+.Contributed by Christian Fetzer in
#​536 <https://github.com/pytest-dev/pytest-cov/pull/536>_.Modernized pytest hook implementation.
Contributed by Bruno Oliveira in
#​549 <https://github.com/pytest-dev/pytest-cov/pull/549>_and Ronny Pfannschmidt in
#​550 <https://github.com/pytest-dev/pytest-cov/pull/550>_.Configuration
📅 Schedule: (in timezone Europe/Stockholm)
* 18-23,0-5 * * 1-5)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.