#27391: Support unittest.TestCase.debug() method
-------------------------------------+-------------------------------------
Reporter: Pavel Savchenko | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: 1.10
Severity: Normal | Resolution:
Keywords: unittest | Triage Stage: Accepted
SimpleTestCase debug |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Pavel Savchenko):
As for other test runners, here's now nose2 invokes a debugger (IIRC
pytest does something similar):
https://github.com/nose-
devs/nose2/blob/master/nose2/plugins/debugger.py#L41-L60
This means that the `post_mortem` is invoked only after the exception was
already caught in `SimpleTestCase.__call__` and, for example, the database
was already rolled back. The test frameworks simple have no real way to
examine the state of the application at the time of the error (but only
"after", when it may be too late).
--
Ticket URL: <https://code.djangoproject.com/ticket/27391#comment:4>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.87c76ff1b349f7a6c23581517f15e934%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
