On Thursday, January 9, 2020 at 6:04:20 AM UTC-5, Edward K. Ream wrote: > > On Tue, Jan 7, 2020 at 1:24 PM Brian Theado <[email protected]> > wrote: > > > I still think full line-by-line coverage analysis will be very valuable. > > I agree. I have just created #1474 > <https://github.com/leo-editor/leo-editor/issues/1474> for this. >
Many thanks for suggesting this. `pytest --cov` has quickly become one of my favorite tools, on a par with pyflakes and pylint. pytest is easy to configure, and it's easy to suppress coverage test within the code itself. leo-editor/.coveragerc now contains the default settings. I've retired some cruft based on the coverage tests and suppressed various helper classes and debug code. The remaining uncovered code are all significant. The code is now up to 82% coverage. The number should be 100% before announcing the project. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/0ab04a4d-cca1-4007-af60-1c8170ac38e3%40googlegroups.com.
