Friday 23 September 2011 — This is 13 years old. Be careful.
Coverage.py v3.5.1 is available. If you haven’t tried it before, coverage.py is a code coverage tool for your Python code. Run your tests under it, and it will tell you which parts of your code are not being exercised by your tests.
As I mentioned in the 3.5.1b1 announcement, there’s not much new: the one new feature is for people measuring coverage on a number of different machines, then combining the data together for reporting. Now you can specify how differently-named source directories on those machines get combined together. The only improvement since 3.5.1b1 is that this feature now works!
Branch coverage works better on “for-else” structures, and on the “with” statement, so if you’ve been experimenting with branch coverage, but have been frustrated by false warnings, this release should be much better.
Comments
One small question, I'm using it with python code involving the eval function. The evaluated piece of code calls a function in another python file. Surprisingly these file and function does not show up in the coverage log. Any idea?
Henri.
Thanks anyway, and again, thanks for the hard work!
Add a comment: