Fixed #4226 -- Added DATABASE_NAME to the list of settings required to be
mentioned in the settings file for the tests to run. Thanks, Paul Smith. git-svn-id: http://code.djangoproject.com/svn/django/trunk@5160 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
a374bf9d50
commit
00d2fb7e70
|
@ -396,10 +396,11 @@ To run the tests, ``cd`` to the ``tests/`` directory and type::
|
|||
./runtests.py --settings=path.to.django.settings
|
||||
|
||||
Yes, the unit tests need a settings module, but only for database connection
|
||||
info -- the ``DATABASE_ENGINE``, ``DATABASE_USER`` and ``DATABASE_PASSWORD``.
|
||||
You will also need a ``ROOT_URLCONF`` setting (its value is ignored; it just
|
||||
needs to be present) and a ``SITE_ID`` setting (any integer value will do) in
|
||||
order for all the tests to pass.
|
||||
info -- the ``DATABASE_NAME`` (required, but will be ignored),
|
||||
``DATABASE_ENGINE``, ``DATABASE_USER`` and ``DATABASE_PASSWORD`` settings. You
|
||||
will also need a ``ROOT_URLCONF`` setting (its value is ignored; it just needs
|
||||
to be present) and a ``SITE_ID`` setting (any integer value will do) in order
|
||||
for all the tests to pass.
|
||||
|
||||
The unit tests will not touch your existing databases; they create a new
|
||||
database, called ``django_test_db``, which is deleted when the tests are
|
||||
|
|
Loading…
Reference in New Issue