The coverage measurement tool for Python. Maintained by @nedbat. No longer here, moved to Mastodon: https://xitter.cf/t.co/7nNXErA6UQ
Joined November 2019
- Tweets148
- Following3
- Followers903
- Likes27
Coverage․py will be posting on Mastodon now: hachyderm.io/@coveragepy See you there!
(From hachyderm.io/@nedbat/1097617…)
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:
github.com/nedbat/coveragepy…
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 7.0 is out, but you might need to update your settings! Let me know how it goes…
(Also at hachyderm.io/@nedbat/1095398…)
Coverage.py retweeted
I’m posting on Mastodon these days, including this announcement of a beta of coverage․py 7.0.0: hachyderm.io/@nedbat/1094514…
Please try it and let me know if it works or if it doesn’t!
New beta! Coverage․py 7.0.0b1 is out: pypi.org/project/coverage/7.…
Many small improvements to path handling and combining data, plus markdown tables. Things might be broken! Let me know, please?
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!
github.com/nedbat/coveragepy…
(also need opinions about how to report...)
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?
github.com/nedbat/coveragepy…
Should coverage․py report on excluded lines that were actually executed? How would you want that to work?
github.com/nedbat/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: pypi.org/project/coverage/6.…
Changes: coverage.readthedocs.io/en/6…
Coverage.py retweeted
“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.”
nedbatchelder.com/blog/20221…
Coverage.py retweeted
I don't use pytest-cov -- here's what I do instead -- youtu.be/sPgvHGkmd0U
Coverage.py retweeted
today's video is about "code coverage" (and uses @coveragepy as an example and shows how to get started with it) -- check it out! youtu.be/eQM3TOjsM_Q
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?
github.com/nedbat/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!
coverage.readthedocs.io/en/6…
pypi.org/project/coverage/6.…
This is the lowest-tech version of coverage measurement ever! 😅
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:
ALT A confusing traceback, with a 1/0 ZeroDivisionError showing how we got to the code. Full text at https://gist.github.com/ad8cef4f71f3398ddc94577abdd7cfa8
Coverage.py retweeted
Using GitHub actions to create a badge with your coverage total: nedbatchelder.com/blog/20220…
Coverage․py 6.4.4, with 3.11 wheels! pypi.org/project/coverage/6.…
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!
