Refs #24622 -- Documented alternatives to some test response attributes when using alternative template engines.

1 files changed, 17 insertions, 0 deletions

diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index 0c97a67267..43255fa589 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -452,6 +452,14 @@ Specifically, a ``Response`` object has the following attributes:
             >>> response.context['name']
             'Arthur'
 
+        .. admonition:: Not using Django templates?
+
+            This attribute is only populated when using the
+            :class:`~django.template.backends.django.DjangoTemplates` backend.
+            If you're using another template engine,
+            :attr:`~django.template.response.SimpleTemplateResponse.context_data`
+            may be a suitable alternative on responses with that attribute.
+
     .. method:: json(**kwargs)
 
         .. versionadded:: 1.9
@@ -488,6 +496,15 @@ Specifically, a ``Response`` object has the following attributes:
         loaded from a file. (The name is a string such as
         ``'admin/index.html'``.)
 
+        .. admonition:: Not using Django templates?
+
+            This attribute is only populated when using the
+            :class:`~django.template.backends.django.DjangoTemplates` backend.
+            If you're using another template engine,
+            :attr:`~django.template.response.SimpleTemplateResponse.template_name`
+            may be a suitable alternative if you only need the name of the
+            template used for rendering.
+
     .. attribute:: resolver_match
 
         An instance of :class:`~django.core.urlresolvers.ResolverMatch` for the