summaryrefslogtreecommitdiff
path: root/docs/topics/testing
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2015-04-13 09:42:43 -0400
committerTim Graham <timograham@gmail.com>2015-04-13 09:42:43 -0400
commit019eaacefc162dc899195836af0ccd231c288ed8 (patch)
treea13915e33b0142b2597a75589a4b9ecd65e53952 /docs/topics/testing
parentb178c02785c7a6a289531e72378119f212df1353 (diff)
[1.6.x] Fixed sphinx errors in docs.
Diffstat (limited to 'docs/topics/testing')
-rw-r--r--docs/topics/testing/tools.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index a2fbf3cf68..2159cce3c9 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -449,7 +449,7 @@ block or :meth:`~unittest.TestCase.assertRaises` to test for exceptions.
The only exceptions that are not visible to the test client are
:class:`~django.http.Http404`,
-:class:`~django.core.exceptions.PermissionDenied`, :exc:`SystemExit`, and
+:class:`~django.core.exceptions.PermissionDenied`, ``SystemExit``, and
:class:`~django.core.exceptions.SuspiciousOperation`. Django catches these
exceptions internally and converts them into the appropriate HTTP response
codes. In these cases, you can check ``response.status_code`` in your test.