#26840: Extract database teardown from DiscoverRunner, to better support third-
party test runners
------------------------------------------------+------------------------
Reporter: carljm | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Currently if a third-party test runner wants access to the default
database teardown code, it has to instantiate a DiscoverRunner in order to
call its `teardown_databases` method. This logic should be extracted into
a standalone utility, like `setup_databases` already is.
Fortunately, Andreas Pelme has already done this in
https://github.com/django/django/pull/6872 -- just filing a supporting
Trac ticket to properly observe the forms.
--
Ticket URL: <https://code.djangoproject.com/ticket/26840>
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/049.f632405d0cbe30fdbe203e236178284d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
