diff options
| author | Russell Keith-Magee <russell@keith-magee.com> | 2007-07-28 07:27:53 +0000 |
|---|---|---|
| committer | Russell Keith-Magee <russell@keith-magee.com> | 2007-07-28 07:27:53 +0000 |
| commit | 5b898f3f94398aff93b698ecb90213c93269978f (patch) | |
| tree | 704ccc8c2570d34c09d0a77a8d442a335f66a599 /docs | |
| parent | 650cea9170313d9a2197d4050f6dcabaaeaa3b20 (diff) | |
Fixed #4995 -- Fixed some problems in documentation ReST formatting. Thanks, Simon G.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5770 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/testing.txt | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/testing.txt b/docs/testing.txt index 7f47e90b19..f4b78273ce 100644 --- a/docs/testing.txt +++ b/docs/testing.txt @@ -581,7 +581,7 @@ name of the test case to the label on the command line:: $ ./manage.py test animals.AnimalTestCase -**New in Django development version:**To run a single test method inside a +**New in Django development version:** To run a single test method inside a test case, add the name of the test method to the label:: $ ./manage.py test animals.AnimalTestCase.testFluffyAnimals @@ -681,12 +681,15 @@ can call it anything you want. The only requirement is that it has the same arguments as the Django test runner: ``run_tests(test_labels, verbosity=1, interactive=True, extra_tests=[])`` + **New in Django development version:** ``test_labels`` is a list of strings describing the tests to be run. A test label can take one of three forms: + * ``app.TestCase.test_method`` - Run a single test method in a test case * ``app.TestCase`` - Run all the test methods in a test case * ``app`` - Search for and run all tests in the named application. + If ``test_labels`` has a value of ``None``, the test runner should run search for tests in all the applications in ``INSTALLED_APPS``. @@ -697,7 +700,7 @@ same arguments as the Django test runner: **New in Django development version:** If ``interactive`` is ``True``, the test suite may ask the user for instructions when the test suite is executed. An example of this behavior would be asking for permission to - delete an existing test database. If ``interactive`` is ``False, the + delete an existing test database. If ``interactive`` is ``False``, the test suite must be able to run without any manual intervention. ``extra_tests`` is a list of extra ``TestCase`` instances to add to the |
