On Jan 27, 5:00 pm, Oleg Oltar <oltarase...@gmail.com> wrote:
> So if I have to store a User object in db (with fields (name, email, pass)
> How should I define the fixture? Should I define it in setup?
When I created my fixtures for my tests, I did ran[1]
./manage.py dumpdata auth > auth.json
Then I just edited auth.json to contain what I wanted. I removed all
but one user from the JSON and set the fields as I needed. Then I
just did the fixture loading as mentioned. I don't know anything
about Nose to know if this will work for you.
Also, I did set my password to a dummy password before the export so
that the password field in the fixture doesn't contain a real password
I want kept safe. It is encrypted, but no reason to put even an
encrypted password in version control.
[1] http://docs.djangoproject.com/en/dev/ref/django-admin/#dumpdata
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
