#14986: TestCase: increase verbosity for TestCase.fixtures usage
----------------------------------------+-----------------------------------
Reporter: carsten | Owner: nobody
Status: closed | Milestone:
Component: Testing framework | Version: 1.2
Resolution: wontfix | Keywords: fixtures
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
This has been proposed before; see #12682, #7134, #4371. I'm sympathetic
to the underlying problem, but it isn't a simple as 'just bump the
verbosity'.
Firstly, there is the problem is determining when the debug message will
be printed (and how often it will be printed). Fixtures are loaded at the
start of every test method; the volume of "fixture loaded" messages would
very rapidly swamp the useful information about the test run.
There is also an implementation issue of how to discover an appropriate
level of verbosity; an individual test case doesn't have exposure to the
verbosity at which it is being run.
Closing wontfix because there isn't a clear action to implement. If anyone
cares to make a practical suggestion -- including a patch -- feel free to
reopen.
--
Ticket URL: <http://code.djangoproject.com/ticket/14986#comment:1>
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-upda...@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.
