mirrors/django
mirrors/django
0
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-11-29 06:03:25 +01:00
Code Issues Releases Wiki Activity

Updated docs to reflect new tests layout.

Browse Source 
Thanks to Ramiro Morales for the initial patch.
This commit is contained in:
Florian Apolloner 2013-02-26 15:00:16 +01:00
parent 4d9f39f307
commit 28e545c4b3
1 changed files with 5 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/internals/contributing/writing-code/unit-tests.txt
View File

@ -7,10 +7,8 @@ code base. It's our policy to make sure all tests pass at all times.
The tests cover:
* Models and the database API (``tests/modeltests``),
* Everything else in core Django code (``tests/regressiontests``),
* :ref:`contrib-apps` (``django/contrib/<app>/tests`` or
``tests/regressiontests/<app>_...``).
* Models, the database API and everything else in core Django core (``tests/``),
* :ref:`contrib-apps` (``django/contrib/<app>/tests`` or ``tests/<app>_...``).
We appreciate any and all contributions to the test suite!
@ -105,9 +103,9 @@ internationalization, type:
./runtests.py --settings=path.to.settings generic_relations i18n
How do you find out the names of individual tests? Look in
``tests/modeltests`` and ``tests/regressiontests`` — each directory name
there is the name of a test. Contrib app names are also valid test names.
How do you find out the names of individual tests? Look in ``tests/`` — each
directory name there is the name of a test. Contrib app names are also valid
test names.
If you just want to run a particular class of tests, you can specify a list of
paths to individual test classes. For example, to run the ``TranslationTests``