From 468d06109778e3656229ac28c9019ea7246f9b79 Mon Sep 17 00:00:00 2001 From: Chris Wedgwood Date: Thu, 29 Sep 2022 04:58:45 +0100 Subject: [PATCH] Fixed #33026 -- Mentioned RequestFactory in testing tools docs. --- docs/topics/testing/tools.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index bdbe756a90..1f235d920b 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 ----------------------------