Coverage.py

Coverage․py will be posting on Mastodon now: @coveragepy" target="_blank" rel="nofollow noopener">hachyderm.io/@coveragepy See you there!

(From @nedbat/109761766482720024" target="_blank" rel="nofollow noopener">hachyderm.io/@nedbat/109761…) 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/coverag…

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

@coveragepy Indeed. Coverage is now reported at 0%. Cannot reproduce it locally. github.com/jugmac00/hibpc… Could you give a pointer which settings have changed? Is there an upgrade guide?

Coverage․py 7.0 is out, but you might need to update your settings! Let me know how it goes… (Also at @nedbat/109539884502986920" target="_blank" rel="nofollow noopener">hachyderm.io/@nedbat/109539…)

I’m posting on Mastodon these days, including this announcement of a beta of coverage․py 7.0.0: @nedbat/109451436366736576" target="_blank" rel="nofollow noopener">hachyderm.io/@nedbat/109451… 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/covera… 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!
#issuecomment-1331961839" target="_blank" rel="nofollow noopener">github.com/nedbat/coverag… (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/coverag…

Should coverage․py report on excluded lines that were actually executed? How would you want that to work? github.com/nedbat/coverag…

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/covera… Changes: #version-6-6-0b1-2022-10-31" target="_blank" rel="nofollow noopener">coverage.readthedocs.io/en/6.6.0b1/cha…

“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/202210/id…

I don't use pytest-cov -- here's what I do instead -- youtu.be/sPgvHGkmd0U

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? #issuecomment-1264741964" target="_blank" rel="nofollow noopener">github.com/nedbat/coverag…

Coverage․py 6.5.0: small changes, but packaging is slightly different. JSON report now has branch details. Let me know how it goes! #changes-6-5-0" target="_blank" rel="nofollow noopener">coverage.readthedocs.io/en/6.5.0/chang… pypi.org/project/covera…

@dbritto_dev Thanks so much! <3

@coveragepy It's closed :)

Anyone want to help with coverage․py on Pyodide? github.com/nedbat/coverag…

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

Using GitHub actions to create a badge with your coverage total: nedbatchelder.com/blog/202209/ma…

Coverage․py 6.4.4, with 3.11 wheels! pypi.org/project/covera… 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!