Changeset 3833
- Timestamp:
- 09/25/06 12:22:59 (2 years ago)
- Files:
-
- django/trunk/docs/contributing.txt (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/contributing.txt
r3771 r3833 260 260 261 261 The Django tests all use the testing infrastructure that ships with Django for 262 testing applications. See `Testing Django Applications`_ for an explanation of262 testing applications. See `Testing Django applications`_ for an explanation of 263 263 how to write new tests. 264 264 265 .. _Testing Django Applications: http://www.djangoproject.com/documentation/testing/265 .. _Testing Django applications: http://www.djangoproject.com/documentation/testing/ 266 266 267 267 Running the unit tests … … 274 274 Yes, the unit tests need a settings module, but only for database connection 275 275 info -- the ``DATABASE_ENGINE``, ``DATABASE_USER`` and ``DATABASE_PASSWORD``. 276 You will also need a ``ROOT_URLCONF`` setting (it 's value is ignored; it just276 You will also need a ``ROOT_URLCONF`` setting (its value is ignored; it just 277 277 needs to be present) and a ``SITE_ID`` setting (any integer value will do) in 278 278 order for all the tests to pass.
