From ab3b5b2380120752f9892c9d0d9dea3ad945c62a Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Thu, 16 Jul 2009 23:49:27 +0000 Subject: [PATCH] [1.0.X] Fixed #10908 -- Clarified the procedure for creating test users 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 --- docs/topics/testing.txt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt index f4f289ccd7..26ecfee24f 100644 --- a/docs/topics/testing.txt +++ b/docs/topics/testing.txt @@ -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()