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 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!
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
Coverage.py retweeted
Using GitHub actions to create a badge with your coverage total: nedbatchelder.com/blog/20220…
Coverage.py retweeted
We're releasing Slipcover v0.1.8, with:
- CPython 3.11 support;
- tentative PyPy support, contributed by Carl Friedrich Bolz-Tereick;
- a tweak in the missing lines output;
Coverage.py retweeted
We just brought out Slipcover v0.1.1, with improved pytest support (it now measures coverage within test files as well). @chriswithers13 @coveragepy
Coverage.py retweeted
Finally get to use @coveragepy context reporting feature for the first time today 🤯 Don't know why I didn't use it sooner.
$ coverage html --show-contexts
It tells "which test run this code".
Doc: coverage.readthedocs.io/en/6…
Coverage.py retweeted
Why your #python mock still doesn't work: nedbatchelder.com/blog/20220…
(tl;dr: use autospec=True!)
Coverage.py retweeted
I will help you! Come debug issues!
Would you like to help coverage․py but aren’t ready for the intricacies of its code? We always need help debugging reported issues, even just to keep track of who is seeing what behavior.
Do you like puzzles? We have ‘em! Get in touch.
Example: github.com/nedbat/coveragepy…
Coverage.py retweeted
I'm delighted to announce that I just released #pytest 7.0.0! This release took a long time, containing over a year of development since 6.2.0. More type annotations, more pathlib (and less py.path) and less pitfalls in the API. See docs.pytest.org/en/7.0.x/ann… for more details.
Coverage.py retweeted
Just me and my buddy @coveragepy! 👋
pyreadiness.org/3.11
ALT Python 3.11 readiness page with only urllib3 and coverage packages marked green for "ready"
Coverage.py retweeted
Combine Coverage for Different Python Versions #python jugmac00.github.io/blog/comb…
Coverage.py retweeted
I wrote a #pytest plugin (of sorts) to evenly balance tests across xdist workers: nedbatchelder.com/blog/20211…
Maybe it can be improved?
Coverage.py retweeted
Speaking of Python 3.11 (and since it is 11/11 11:11): it's fast! My totally not scientific experiment (running an Advent of Code solution) says it is 30% faster than 3.10!
Go try 3.11!
Coverage․py 6.1.2: a few fixes, but mostly: Python 3.11 support! Why not take it for a spin?
coverage.readthedocs.io/en/6…
Coverage.py retweeted
Flexibly total your coverage and check it against goals: nedbatchelder.com/blog/20211…
Coverage.py retweeted
It was a blast to spend an hour with Will and Carlton talking about Django, startups, open source, testing, and walking!
This Post is from an account that no longer exists. Learn more
Coverage.py retweeted
Coverage Is Not Strongly Correlated with Test Suite Effectiveness
neverworkintheory.org/2021/0…
Coverage.py retweeted
Do you know which lines of your code are covered by which tests? Why would you even want to know this?
Find out in my latest blog post:
"Enrich Test Coverage With Contexts"
jugmac00.github.io/blog/enri…
#python #pytest #coverage