From 9beca95eb0f2b5c19b6f7824fd75326527132566 Mon Sep 17 00:00:00 2001 From: Thomas Grainger Date: Wed, 24 Sep 2014 14:57:07 +0100 Subject: [1.6.x] Added SuspiciousOperation to list of caught exceptions in testing docs. Backport of 21683011d5 from master --- docs/topics/testing/tools.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'docs/topics/testing') diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index 583b1834b8..6f770bd1b2 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -447,10 +447,12 @@ If you point the test client at a view that raises an exception, that exception will be visible in the test case. You can then use a standard ``try ... except`` block or :meth:`~unittest.TestCase.assertRaises` to test for exceptions. -The only exceptions that are not visible to the test client are ``Http404``, -``PermissionDenied`` and ``SystemExit``. 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. +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.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. Persistent state ~~~~~~~~~~~~~~~~ -- cgit v1.3