Proofread changes to docs/contributing.txt from [3771]

git-svn-id: http://code.djangoproject.com/svn/django/trunk@3833 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2006-09-25 17:22:59 +00:00
parent 205cb040d4
commit 40aa0ca875
1 changed files with 3 additions and 3 deletions

View File

@ -259,10 +259,10 @@ The tests cover:
We appreciate any and all contributions to the test suite! We appreciate any and all contributions to the test suite!
The Django tests all use the testing infrastructure that ships with Django for The Django tests all use the testing infrastructure that ships with Django for
testing applications. See `Testing Django Applications`_ for an explanation of testing applications. See `Testing Django applications`_ for an explanation of
how to write new tests. how to write new tests.
.. _Testing Django Applications: http://www.djangoproject.com/documentation/testing/ .. _Testing Django applications: http://www.djangoproject.com/documentation/testing/
Running the unit tests Running the unit tests
---------------------- ----------------------
@ -273,7 +273,7 @@ To run the tests, ``cd`` to the ``tests/`` directory and type::
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_ENGINE``, ``DATABASE_USER`` and ``DATABASE_PASSWORD``.
You will also need a ``ROOT_URLCONF`` setting (it's value is ignored; it just 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 needs to be present) and a ``SITE_ID`` setting (any integer value will do) in
order for all the tests to pass. order for all the tests to pass.