cuvner 16.2.0

Other Neat Visualizations

Other nice “coverage visualization” tools I’ve run across:

• of course, Coverage.py itself comes with a nice HTML visualization

• emacs-coverage

• codecov.io browser extension shows coverage live while browsing github

cuv graph

This displays all the files in your project and a histogram-like graph of their coverage. Each character represents 8 lines of code, and uses a group of unicode characters (0x2580 through 0x2587) to draw a little graph. So, if those 8 lines are not covered at all, the graph will be all red; if they’re all covered, it will be all green. If 2 out of the 8 lines are covered, there will be about 25% green and the rest red.

The total size of each file can thus be easily seen (by the length of the histogram part, which wraps to subsequent lines if needed) and an idea of which parts are covered is given.

TODO:

• testing on more terminal types

• how does it look when using something besides Solarized Dark?

• useful, beyond eye-candy?

cuv lessopen

This command is intended to be used via the LESSOPEN environment variable, which lets you pre-process files that are opened with less. So, once set up (see the help via cuv lessopen --help) you can simply run less on any file in your project, and it will get syntax-highlighted and show you the line-by-line coverage with a leading green or red mini-verical bar and red background (for uncovered lines).

A header appears at the top showing the total coverage for this particular file.

TODO:

• probably the “proper” way to do this is via a Pygments plugin or extension of some sort

• option to change which Pygments style is used

• dark/light background option?

cuv diff

You can pipe a git diff to this and see a colorized version of the diff in your console. I am using a library called unidiff to read the actual diff, which so far works quite nicely. That said, I’ve only tried against the output of Git, like so:

git diff | cuv diff | less

TODO:

• colors are unsatisfying, since for added lines they’re pretty much the same as Git’s colored output

• maybe make it look more like the “real” underlying diff? (e.g. re-create the @@ and so forth things)

• does it work with merge commits?

cuv spark

This shows a “spark-line” sort of thing in the console. It’s not very useful for big projects (e.g. Twisted), but gives a very quick overview of the coverage in a small amount of space. Using the same unicode characters as cuv graph, this represents each file as a single character, and its percentage coverage is graphed (so you only get granularity down to about 12.5%).