1 | Index: docs/testing.txt |
---|
2 | =================================================================== |
---|
3 | --- docs/testing.txt (revisión: 4347) |
---|
4 | +++ docs/testing.txt (copia de trabajo) |
---|
5 | @@ -244,11 +244,11 @@ |
---|
6 | |
---|
7 | ``login(path, username, password)`` |
---|
8 | In a production site, it is likely that some views will be protected with |
---|
9 | - the @login_required URL provided by ``django.contrib.auth``. Interacting |
---|
10 | + the @login_required decorator provided by ``django.contrib.auth``. Interacting |
---|
11 | with a URL that has been login protected is a slightly complex operation, |
---|
12 | - so the Test Client provides a simple URL to automate the login process. A |
---|
13 | + so the Test Client provides a simple method to automate the login process. A |
---|
14 | call to ``login()`` stimulates the series of GET and POST calls required |
---|
15 | - to log a user into a @login_required protected URL. |
---|
16 | + to log a user into a @login_required protected view. |
---|
17 | |
---|
18 | If login is possible, the final return value of ``login()`` is the response |
---|
19 | that is generated by issuing a GET request on the protected URL. If login |
---|