Hi There, >>> We don't even ensure that every statement of code >>> gets executed at least once. >> >> Mike Hansen posted some code to use a tool to check that (a long time >> ago). I imagine that after doctest coverage is up to 100% function >> coverage that there will be a new push to then get the statement coverage >> up to 100%. It would be interesting even now to see how much statement >> coverage lagged behind function coverage. > > That would be very interesting indeed. I don't think it'll be too long > before we have line profilers fully supported (and hence coverage tools > too) for Cython as well as Python code. I'm not sure what tools there are > to deal with branch coverage.
+10 !!! See my message on the same thread. There are several files in sage which are never executed. Having an automatic way to check that could be a good way to find them, deprecate and remove them. As I said, I'd better remove unused code that adding doctests to it. Cheers, Florent -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
