diff options
| author | Kevin Christopher Henry <k@severian.com> | 2013-08-22 04:39:31 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-08-22 09:39:21 -0400 |
| commit | 1b236048b9a915296dc13081fad7bb75d0ff1f4d (patch) | |
| tree | fe127db27ecb6c1c6804aebdd757324436c6bb54 /docs | |
| parent | 3b32b1544f7d1ff885d2cd7f4c96a6e5025e4725 (diff) | |
[1.5.x] Documentation -- Clarified use of 'view' in test client introduction.
Backport of 2e926b041c from master
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/testing/overview.txt | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt index 58694a6e3f..ea475e0299 100644 --- a/docs/topics/testing/overview.txt +++ b/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 short: -* 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 |