diff options
| author | Russell Keith-Magee <russell@keith-magee.com> | 2007-07-20 14:07:54 +0000 |
|---|---|---|
| committer | Russell Keith-Magee <russell@keith-magee.com> | 2007-07-20 14:07:54 +0000 |
| commit | bdc5a3eb51f42946ef6d56333edaff16caeecb34 (patch) | |
| tree | aff6f5a9cac4e2f2619513897eab589a43f68498 | |
| parent | 9922a04bb6a9587aee197c6d0e87de9e5bd7e240 (diff) | |
Refs #3782 -- Added documentation note that suite() handling is only in development version.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5730 bcc190cf-cafb-0310-a4f2-bffc1f526a37
| -rw-r--r-- | docs/testing.txt | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/testing.txt b/docs/testing.txt index 0d59ad742c..704d224daa 100644 --- a/docs/testing.txt +++ b/docs/testing.txt @@ -123,6 +123,8 @@ to find all the test cases (that is, subclasses of ``unittest.TestCase``) in ``models.py`` and ``tests.py``, automatically build a test suite out of those test cases, and run that suite. +**New in Django development version** + However, if you define a method called ``suite()`` in either ``models.py`` or ``tests.py``, that method will be used to construct the test suite for that module. This follows the `suggested organization`_ for unit tests. See the |
