On Tue, Apr 6, 2010 at 12:42, C. Titus Brown <c...@msu.edu> wrote: > On Tue, Apr 06, 2010 at 10:36:14PM +0300, anatoly techtonik wrote: > > On Tue, Apr 6, 2010 at 7:31 PM, Georg Brandl <g.bra...@gmx.net> wrote: > > > > > >>>> Where can I find public reports with Python tests code coverage? > > >>> > > >>> Here: > > >>> > > >>> http://coverage.livinglogic.de/ > > >> > > >> Thank you. What is the status of getting these stats on python.org? > > > > > > Wouldn't "status" imply that there is a plan to do so? > > > > It is not that hard to create that plan given that there is a fair > > amount of developers who care about code coverage. > > Anatoly, > > nonetheless, I don't know of any plan :). > > I keep on shaving yaks when trying to get test coverage posted somewhere; > it's actually not a trivial problem to set it up automatically and > reliably, in my experience. If you are interested in volunteering to > help, I'm sure it would be appreciated -- I suspect the right place to > start would be get test coverage running reproducibly and reliably on > your own machines and posted somewhere; then you could ask for permissions > to post it somewhere on *.python.org. (I don't see why we care where it's > posted, but that's what you asked about.) > > I keep on running into technical barriers in getting cross-platform code > coverage analysis working, which would be quite valuable; it's easy to > get it working once, but to keep it working is a maintenance task that > involves regular effort, again, in my experience. >
And just in general, it requires someone stepping forward to do it. While there might be several developers who find test coverage important (me included), it's a matter of taking the time to set up something that will work. For me personally that is more time than I have for my volunteer work for Python as I have other things that I put at a higher priority. It's an overused, worn out statement, but it's open source so stuff only gets done when someone REALLY has the desire and time to do something. I'm grateful that Walter has done what he has. If someone steps forward to write up instructions on how to run figleaf or coverage.py over the test suite then that would be appreciated. But just because something isn't technically hard, doesn't mean it isn't hard from the perspective of time and motivation. -Brett
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
