summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/testing/tools.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index 61788d2c1d..c4f64fef94 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -34,12 +34,15 @@ short:
* Use Django's test client to establish that the correct template is being
rendered and that the template is passed the correct context data.
+* Use :class:`~django.test.RequestFactory` to test view functions directly,
+ bypassing the routing and middleware layers.
+
* Use in-browser frameworks like Selenium_ to test *rendered* HTML and the
*behavior* of web pages, namely JavaScript functionality. Django also
provides special support for those frameworks; see the section on
:class:`~django.test.LiveServerTestCase` for more details.
-A comprehensive test suite should use a combination of both test types.
+A comprehensive test suite should use a combination of all of these test types.
Overview and a quick example
----------------------------