Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update pytest-cov to 4.1.0 #51

Closed
wants to merge 1 commit into from

Conversation

pyup-bot
Copy link
Collaborator

This PR updates pytest-cov from 3.0.0 to 4.1.0.

Changelog

4.1.0

------------------

* Updated CI with new Pythons and dependencies.
* Removed rsyncdir support. This makes pytest-cov compatible with xdist 3.0.
Contributed by Sorin Sbarnea in `558 <https://github.com/pytest-dev/pytest-cov/pull/558>`_.
* Optimized summary generation to not be performed if no reporting is active (for example,
when ``--cov-report=''`` is used without ``--cov-fail-under``).
Contributed by Jonathan Stewmon in `589 <https://github.com/pytest-dev/pytest-cov/pull/589>`_.
* Added support for JSON reporting.
Contributed by Matthew Gamble in `582 <https://github.com/pytest-dev/pytest-cov/pull/582>`_.
* Refactored code to use f-strings.
Contributed by Mark Mayo in `572 <https://github.com/pytest-dev/pytest-cov/pull/572>`_.
* Fixed a skip in the test suite for some old xdist.
Contributed by a bunch of people in `565 <https://github.com/pytest-dev/pytest-cov/pull/565>`_.

4.0.0

------------------

**Note that this release drops support for multiprocessing.**


* `--cov-fail-under` no longer causes `pytest --collect-only` to fail
Contributed 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 was
mostly 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.py`` by 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/issues/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>`_.
Links

@codecov
Copy link

codecov bot commented May 24, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (45adbb8) 100.00% compared to head (bb09732) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##            master       #51   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           26        26           
=========================================
  Hits            26        26           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@pyup-bot
Copy link
Collaborator Author

Closing this in favor of #63

@pyup-bot pyup-bot closed this Mar 24, 2024
@aragilar aragilar deleted the pyup-update-pytest-cov-3.0.0-to-4.1.0 branch March 24, 2024 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant