innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

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:
Malcolm Tredinnick 2007-05-08 02:33:10 +00:00
parent a374bf9d50
commit 00d2fb7e70
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/contributing.txt
View File

@ -396,10 +396,11 @@ To run the tests, ``cd`` to the ``tests/`` directory and type::
./runtests.py --settings=path.to.django.settings ./runtests.py --settings=path.to.django.settings
Yes, the unit tests need a settings module, but only for database connection Yes, the unit tests need a settings module, but only for database connection
info -- the ``DATABASE_ENGINE``, ``DATABASE_USER`` and ``DATABASE_PASSWORD``. info -- the ``DATABASE_NAME`` (required, but will be ignored),
You will also need a ``ROOT_URLCONF`` setting (its value is ignored; it just ``DATABASE_ENGINE``, ``DATABASE_USER`` and ``DATABASE_PASSWORD`` settings. You
needs to be present) and a ``SITE_ID`` setting (any integer value will do) in will also need a ``ROOT_URLCONF`` setting (its value is ignored; it just needs
order for all the tests to pass. 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 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 database, called ``django_test_db``, which is deleted when the tests are