Coverage.py

The coverage measurement tool for Python. Maintained by @nedbat.

No longer here, moved to Mastodon:

[Coverage.py @coveragepy]

Coverage․py will be posting on Mastodon now: https://t.co/7TqAfMhgaz See you there!

[Coverage.py @coveragepy]

(From https://t.co/oPeAs1CzaF)

Have you wanted to measure coverage, but exclude certain data points because the lines ran "when it didn't count"?

Help me figure out how to make that possible:
https://t.co/RQUGQctm2Z

[Coverage.py @coveragepy]

@jugmac00 Run with `--debug=trace` to get details of what is being ignored and why. Likely it’s your “omit” setting in tox.ini

[Coverage.py @coveragepy]

Coverage․py 7.0 is out, but you might need to update your settings! Let me know how it goes…

(Also at https://t.co/ibw9FqaW1K)

[Ned Batchelder @nedbat]

I’m posting on Mastodon these days, including this announcement of a beta of coverage․py 7.0.0: https://t.co/YaNVZABkg4

Please try it and let me know if it works or if it doesn’t!

[Coverage.py @coveragepy]

New beta! Coverage․py 7.0.0b1 is out: https://t.co/4UsZaTmZWM

Many small improvements to path handling and combining data, plus markdown tables. Things might be broken! Let me know, please?

[Coverage.py @coveragepy]

When running coverage, lines that should have run but didn't are called "unexecuted." What's a word for the opposite? Lines we said wouldn't run, but did: Sneaks? Surprises? Gremlins? Escapees?
We need ideas!
https://t.co/YXC63jGhOl
(also need opinions about how to report...)

[Coverage.py @coveragepy]

Does PyCharm really use its own --omit switch on the command line? Should coverage․py combine the command line and the config? Or should the command line win like it does now?
https://t.co/QqwblbLf2a

[Coverage.py @coveragepy]

Should coverage․py report on excluded lines that were actually executed? How would you want that to work?
https://t.co/Ror98DPSY7

[Coverage.py @coveragepy]

Coverage․py 6.6.0 beta 1: improvements to file patterns and relative_files that mean you MIGHT have to tweak your settings. Please test this pre-release version and let us know if something isn’t working!
Install: https://t.co/yCasKvV7Qt
Changes: https://t.co/G2Y5Mqq0nM

[Ned Batchelder @nedbat]

“The idea that I can decide my open-source purpose feels a bit like a genie granting me a wish, and then I have to deal with the unanticipated plot twists that result.”

https://t.co/kJ4AThtBzM

[Anthony Sottile @codewithanthony]

I don't use pytest-cov -- here's what I do instead -- https://t.co/1Kp6Xnk7U6

[Anthony Sottile @codewithanthony]

today's video is about "code coverage" (and uses @coveragepy as an example and shows how to get started with it) -- check it out! https://t.co/A08IXN3Zrk

[Coverage.py @coveragepy]

Looking for opinions: when combining data files, should “*/foo” match “foo/bar”? Should relative_files=True mean that we always match file paths by prefixes?
https://t.co/pt3yz7Mqnf

[Coverage.py @coveragepy]

Coverage․py 6.5.0: small changes, but packaging is slightly different. JSON report now has branch details. Let me know how it goes!
https://t.co/wWnlnyC9tW
https://t.co/GMxhXd5Jxr

[Coverage.py @coveragepy]

@dbritto_dev Thanks so much! <3

[Coverage.py @coveragepy]

Anyone want to help with coverage․py on Pyodide?
https://t.co/9ikyHwkpO9

[Coverage.py @coveragepy]

This is the lowest-tech version of coverage measurement ever! 😅

[Ned Batchelder @nedbat]

Need a quick tracer bullet through confusing #Python code? Put "1/0" into the code. Easy to drop in, and it will raise an unlikely and easily identified ZeroDivisionError exception:

[Ned Batchelder @nedbat]

Using GitHub actions to create a badge with your coverage total: https://t.co/eo9vsDrybC

[Coverage.py @coveragepy]

Coverage․py 6.4.4, with 3.11 wheels! https://t.co/uGndJxcXWo

Now is the time to run your test suites on 3.11.0rc1. Python 3.11 is shipping in October, so make sure your code is ready for it!