#10868: _destroy_test_db exposes the production database to possibly destructive
actions from the unit tests
-------------------------------------+-------------------------------------
Reporter: ovidiu | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version:
Severity: Release blocker | Resolution:
Keywords: django.test | Triage Stage: Design
Has patch: 0 | decision needed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by julien):
That sounds like a good proposal. Another slightly different approach
would be to wait indefinitely instead of erroring out. If one spawns new
threads then they should be responsible for cleaning them up. The risk of
damaging the production database is more important to consider than the
risk of breaking some tests.
How would you go about writing tests for this proposal? Since this all
happens before+after the general test suite is run, I'm not sure this
would even be possible.
--
Ticket URL: <https://code.djangoproject.com/ticket/10868#comment:10>
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 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.
