Ned Batchelder

If anyone wants to try some really hacked together functionality as a work in progress: install this temporary branch of coverage.py: ``` python3 -m pip install git+https://github.com/nedbat/coveragepy@nedbat/public-analysis#egg=coverage==0.0 ``` After running...

Thanks. I'm wondering how those tools cope with real projects with thousands of functions. How do they present the information in a useful way?

I've implemented more real function and class reports. Please try them out: https://nedbatchelder.com/blog/202404/try_it_functionclass_coverage_report.html

@kierun: > Breaking it down per file would be cleaner. A summary page could have the top (or bottom?) covered. By that, I mean the top 10 (say?) functions/classes that...

@kierun: >> […] It might not be obvious, but the column headers are click-to-sort […] > > Oh, cool! 😁 This is perfect. Any ideas what can I do to...

Interesting idea. A quick attempt shows that the glyphs don't play nicely, and it's cluttered: Maybe I can just add a line above the table: "Columns are sortable." I know:...

I appreciate the ideas. One benefit of a flat view is that you can sort it by coverage to focus on what needs work no matter where it is.

Thanks for the pointer to genhtml. I'll experiment with that as an escape hatch for people who want more involved reports (once the lcov output has function data).

> ensure that tables are always shown sorted by one of the columns and that the header for that column shows the arrow to indicate the sort state. Currently tables...

(oops, forgot to mention this issue in the changelog, but) this is now released as part of [coverage 7.5.0](https://pypi.org/project/coverage/7.5.0). Try it out!