#4501: Coverage support for tests
----------------------------------------+-----------------------------------
Reporter: b...@almad.net | Owner: ericholscher
Status: new | Milestone:
Component: Testing framework | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by ericholscher):
* owner: adrian => ericholscher
* status: reopened => new
Comment:
Marking this as assigned to me. I have some code that does this
externally. If this can be done in a custom test runner, and requires a
third party module; is there a reason that this shouldn't just be third
party?
Jacob marked it accepted, so I assume this would go in core with a test
import on coverage.py, and if it is there it would be enabled with a flag.
--
Ticket URL: <http://code.djangoproject.com/ticket/4501#comment:6>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
