Absolutely! I actually proposed this as part of my GSoC project. I think there is enough interest that basic coverage support could be seen in core. My research turned up figleaf, which seemed like a better fit (but its an external dependency, and I'm not sure of the django policy on this, especially when coverage.py is already pretty good ). On a vaguely related note, I have been fiddling with the idea of a web interface to some of the TestMaker functionality in Eric's test-utils. Namely, we now serialize the actual request data as opposed to generating tests directly, meaning there are now lots of cool analysis that can be performed on things like template code (finding unused Context values etc.). Integration with real coverage analysis could make for a _wicked_ testing environment.
Just Brain-Farting, relevant subject+slow lecture = worthless devlist posts. -Kevin On Tue, Apr 7, 2009 at 9:58 AM, George Song <gsong...@gmail.com> wrote: > > I did a fair amount of work last week with ``coverage.py``. I came up > with a pretty flexible system which suited my own development needs > but is probably useful to a lot of people out there. > > I noticed there's already a ticket open for this: <http:// > code.djangoproject.com/ticket/4501#comment:10> > > I've commented there as well. I was able to run ``runtests.py`` by > simply specifying my test runner as well. > > My idea was to make it a third-party plugin app with a custom > ``manage.py`` command like ``./manage.py test-coverage [app1 > app2.TestCase app3.TestCase.test...]`` instead of modifying the > existing ``test`` command. > > In any case, here's the actual HTML output, in addition to the console > report that ``coverage.report()`` outputs. > > From my current project: <http://lehrhaus.55minutes.com/test_report/> > From ``runtests.py``: <http://test.55minutes.com/test_report/> > > Please refer to the ticket <http://code.djangoproject.com/ticket/ > 4501#comment:10> for more details. > > > -- Kevin Kubasik http://kubasik.net/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
