diff options
| author | Honza Král <honza.kral@gmail.com> | 2010-01-04 01:06:26 +0000 |
|---|---|---|
| committer | Honza Král <honza.kral@gmail.com> | 2010-01-04 01:06:26 +0000 |
| commit | ffd5564a87c5c8e5d5e1e201ae3462807b955efc (patch) | |
| tree | 80c63887e1e9a9a2d379e655ad038f25f3982697 /docs/topics/testing.txt | |
| parent | a7c320fea79b8750ab2a8aca84d8e8fb76d8b100 (diff) | |
[soc2009/model-validation] Merged to trunk at r12070
git-svn-id: http://code.djangoproject.com/svn/django/branches/soc2009/model-validation@12073 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/topics/testing.txt')
| -rw-r--r-- | docs/topics/testing.txt | 21 |
1 files changed, 19 insertions, 2 deletions
diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt index 9ef6cceae8..a309294d7c 100644 --- a/docs/topics/testing.txt +++ b/docs/topics/testing.txt @@ -242,8 +242,8 @@ in different circumstances. Running tests ============= -Once you've written tests, run them using your project's ``manage.py`` -utility:: +Once you've written tests, run them using the :djadmin:`test` subcommand of +your project's ``manage.py`` utility:: $ ./manage.py test @@ -274,6 +274,23 @@ a test case, add the name of the test method to the label:: $ ./manage.py test animals.AnimalTestCase.testFluffyAnimals +.. versionadded:: 1.2 + You can now trigger a graceful exit from a test run by pressing ``Ctrl-C``. + +If you press ``Ctrl-C`` while the tests are running, the test runner will +wait for the currently running test to complete and then exit gracefully. +During a graceful exit the test runner will output details of any test +failures, report on how many tests were run and how many errors and failures +were encountered, and destroy any test databases as usual. Thus pressing +``Ctrl-C`` can be very useful if you forget to pass the :djadminopt:`--failfast` +option, notice that some tests are unexpectedly failing, and want to get details +on the failures without waiting for the full test run to complete. + +If you do not want to wait for the currently running test to finish, you +can press ``Ctrl-C`` a second time and the test run will halt immediately, +but not gracefully. No details of the tests run before the interruption will +be reported, and any test databases created by the run will not be destroyed. + The test database ----------------- |
