#12122: don't create test database on ./manage.py test
----------------------------------------+-----------------------------------
Reporter: Exe | Owner: nobody
Status: closed | Milestone:
Component: Testing framework | Version: 1.1
Resolution: wontfix | Keywords:
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:
What you propose sounds like extremely dangerous behavior to exist as a
default. If a database already exists, then there's a reasonable chance
that it could contain useful data. If the default behavior of the test
suite is to purge the contents of a database, it would be very easy to
accidentally lose that data through the simple act of running a test
suite.
If you don't like Django's default test setup/teardown procedure, it is
configurable - see
[http://docs.djangoproject.com/en/dev/topics/testing/#defining-a-test-
runner the documentation on writing a custom test runner].
--
Ticket URL: <http://code.djangoproject.com/ticket/12122#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-updates@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
-~----------~----~----~----~------~----~------~--~---
