Skip to content

Commit

Permalink
[1.0.X] Fixed #10908 -- Clarified the procedure for creating test use…
Browse files Browse the repository at this point in the history
…rs in the testing docs. Thanks to gruszczy and timo.

Merge of r11248 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@11254 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information
freakboy3742 committed Jul 16, 2009
1 parent 940b8a1 commit ab3b5b2
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion docs/topics/testing.txt
Original file line number Diff line number Diff line change
Expand Up @@ -596,7 +596,13 @@ arguments at time of construction:
user accounts that are valid on your production site will not work
under test conditions. You'll need to create users as part of the test
suite -- either manually (using the Django model API) or with a test
fixture.
fixture. Remember that if you want your test user to have a password,
you can't set the user's password by setting the password attribute
directly -- you must use the
:meth:`~django.contrib.auth.models.User.set_password()` function to
store a correctly hashed password. Alternatively, you can use the
:meth:`~django.contrib.auth.models.UserManager.create_user` helper
method to create a new user with a correctly hashed password.

.. method:: Client.logout()

Expand Down

0 comments on commit ab3b5b2

Please sign in to comment.