test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #6070 -- Fixed the documentation about running Django's core tests, since SITE_ID is no longer required (it was removed in [6814]). Thanks, beorn. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@6830 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-12-02 15:17:21 +00:00
parent fc4129abbb
commit f610269006
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/contributing.txt
View File

@ -659,9 +659,8 @@ 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, with the ``DATABASE_ENGINE`` setting. You will also need a ``ROOT_URLCONF`` info, with the ``DATABASE_ENGINE`` setting. You'll also need a ``ROOT_URLCONF``
setting (its value is ignored; it just needs to be present) and a ``SITE_ID`` setting (its value is ignored; it just needs to be present).
setting (any non-zero integer value will do) in order for all the tests to pass.
If you're using the ``sqlite3`` database backend, no further settings are If you're using the ``sqlite3`` database backend, no further settings are
needed. A temporary database will be created in memory when running the tests. needed. A temporary database will be created in memory when running the tests.