Browse files

[1.5.x] Documentation -- Clarified use of 'view' in test client intro…


Backport of 2e926b0 from master
  • Loading branch information...
marfire authored and timgraham committed Aug 22, 2013
1 parent 3b32b15 commit 1b236048b9a915296dc13081fad7bb75d0ff1f4d
Showing with 4 additions and 3 deletions.
  1. +4 −3 docs/topics/testing/overview.txt
@@ -362,7 +362,8 @@ Some of the things you can do with the test client are:
everything from low-level HTTP (result headers and status codes) to
page content.
-* Test that the correct view is executed for a given URL.
+* See the chain of redirects (if any) and check the URL and status code at
+ each step.
* Test that a given request is rendered by a given Django template, with
a template context that contains certain values.
@@ -371,8 +372,8 @@ Note that the test client is not intended to be a replacement for Selenium_ or
other "in-browser" frameworks. Django's test client has a different focus. In
-* Use Django's test client to establish that the correct view is being
- called and that the view is collecting the correct context data.
+* 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 in-browser frameworks like Selenium_ to test *rendered* HTML and the
*behavior* of Web pages, namely JavaScript functionality. Django also

0 comments on commit 1b23604

Please sign in to comment.