diff options
| author | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2007-12-02 15:17:21 +0000 |
|---|---|---|
| committer | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2007-12-02 15:17:21 +0000 |
| commit | f610269006255b7df0ea9dc511381cb781d84123 (patch) | |
| tree | 934e8b61366b2d01be69a932afc24be4f7a8c48e /docs | |
| parent | fc4129abbbff3981ed70b7203cf8aeef811242aa (diff) | |
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
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/contributing.txt | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/contributing.txt b/docs/contributing.txt index b34c704d3c..efc6640d10 100644 --- a/docs/contributing.txt +++ b/docs/contributing.txt @@ -659,9 +659,8 @@ 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, with the ``DATABASE_ENGINE`` setting. You will also need a ``ROOT_URLCONF`` -setting (its value is ignored; it just needs to be present) and a ``SITE_ID`` -setting (any non-zero integer value will do) in order for all the tests to pass. +info, with the ``DATABASE_ENGINE`` setting. You'll also need a ``ROOT_URLCONF`` +setting (its value is ignored; it just needs to be present). 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. |
