Changeset 4349
- Timestamp:
- 01/18/07 21:18:36 (2 years ago)
- Files:
-
- django/trunk/docs/testing.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/testing.txt
r4301 r4349 245 245 ``login(path, username, password)`` 246 246 In a production site, it is likely that some views will be protected with 247 the @login_required URLprovided by ``django.contrib.auth``. Interacting247 the @login_required decorator provided by ``django.contrib.auth``. Interacting 248 248 with a URL that has been login protected is a slightly complex operation, 249 so the Test Client provides a simple URLto automate the login process. A249 so the Test Client provides a simple method to automate the login process. A 250 250 call to ``login()`` stimulates the series of GET and POST calls required 251 to log a user into a @login_required protected URL.251 to log a user into a @login_required protected view. 252 252 253 253 If login is possible, the final return value of ``login()`` is the response
