Ticket #4995: testing.diff
File testing.diff, 1.7 KB (added by , 17 years ago) |
---|
-
docs/testing.txt
581 581 582 582 $ ./manage.py test animals.AnimalTestCase 583 583 584 **New in Django development version:** To run a single test method inside a584 **New in Django development version:** To run a single test method inside a 585 585 test case, add the name of the test method to the label:: 586 586 587 587 $ ./manage.py test animals.AnimalTestCase.testFluffyAnimals … … 681 681 same arguments as the Django test runner: 682 682 683 683 ``run_tests(test_labels, verbosity=1, interactive=True, extra_tests=[])`` 684 684 685 **New in Django development version:** ``test_labels`` is a list of 685 686 strings describing the tests to be run. A test label can take one of 686 687 three forms: 688 687 689 * ``app.TestCase.test_method`` - Run a single test method in a test case 688 690 * ``app.TestCase`` - Run all the test methods in a test case 689 691 * ``app`` - Search for and run all tests in the named application. 692 690 693 If ``test_labels`` has a value of ``None``, the test runner should run 691 694 search for tests in all the applications in ``INSTALLED_APPS``. 692 695 … … 697 700 **New in Django development version:** If ``interactive`` is ``True``, the 698 701 test suite may ask the user for instructions when the test suite is 699 702 executed. An example of this behavior would be asking for permission to 700 delete an existing test database. If ``interactive`` is ``False , the703 delete an existing test database. If ``interactive`` is ``False``, the 701 704 test suite must be able to run without any manual intervention. 702 705 703 706 ``extra_tests`` is a list of extra ``TestCase`` instances to add to the