test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Documentation -- Clarified use of 'view' in test client introduction.

This commit is contained in:
Kevin Christopher Henry 2013-08-22 04:39:31 -04:00 committed by Tim Graham
parent bac4d03ce6
commit 2e926b041c
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/topics/testing/overview.txt
View File

@ -328,7 +328,8 @@ Some of the things you can do with the test client are:
everything from low-level HTTP (result headers and status codes) to everything from low-level HTTP (result headers and status codes) to
page content. 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 * Test that a given request is rendered by a given Django template, with
a template context that contains certain values. a template context that contains certain values.
@ -337,8 +338,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 other "in-browser" frameworks. Django's test client has a different focus. In
short: short:
* Use Django's test client to establish that the correct view is being * Use Django's test client to establish that the correct template is being
called and that the view is collecting the correct context data. rendered and that the template is passed the correct context data.
* Use in-browser frameworks like Selenium_ to test *rendered* HTML and the * Use in-browser frameworks like Selenium_ to test *rendered* HTML and the
*behavior* of Web pages, namely JavaScript functionality. Django also *behavior* of Web pages, namely JavaScript functionality. Django also