#3971: Verbose testing framework does not say which test it is about to execute
---------------------------+------------------------------------------------
Reporter: mtredinnick | Owner: russellm
Status: new | Component: Unit test system
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------+------------------------------------------------
Comment (by mtredinnick):
Finally remembered to test this. It doesn't work as I would have thought,
but it's possible my particular stress testing isn't worth solving.
I simulated my previous problems by putting "raise Exception" into
core/management.py on line 732 (just before the call to load_data() in the
flush() function). Then, running all the tests under -v2 exhibits the
expected explosion, but we aren't told what failed.
Thinking about this a bit more, I'm not sure it's worth going to extreme
lengths to account for this behaviour. Detecting that some bozo has stuck
a monkey wrench deep in the guts of management.py might not be easy.
In any case, I've updated the patch to apply against recent trunk, since
there were some changes in the interim and a bit of manual patching was
required.
--
Ticket URL: <http://code.djangoproject.com/ticket/3971#comment:3>
Django Code <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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
