On Mon, Jul 27, 2009 at 6:17 AM, Vitaly Babiy<vbabi...@gmail.com> wrote: > Hey, > I have replaced the default auth backend with my own that requires a field > to be set on my own custom user objects. So when I run my test suite ( which > includes the auth app ) most of the auth test fail. Due to the fact that > djangos fixtures don't create user object of my custom type. What is the > best way to work around this?
There isn't really an easy workaround. If you put contrib.auth in your INSTALLED_APPS, Django assumes - somewhat reasonably - that you are using the User model. One approach that may be worth considering is to look at whether you actually need to put contrib.auth in INSTALLED APPS. If you're just using some of the backend utilities - such as the authentication backends - you may not need to sync the auth application itself. Beyond that, you're into slightly unexplored territory. The hardcore approach would be to just delete the tests directory from contrib.auth. This will make the test failure go away, but that's a bit like saying you can fix your long toenails by amputating your foot :-) There may be a less hardcore solution, but it will require some exploration on your part. It certainly isn't part of an official API at this point. This issue actually covers two problems that I'd like to address in the Django v1.2 timeframe. Firstly, differentiating between integration tests and release tests; secondly, making the User model truly pluggable, especially with respect to contrib.admin. Any feedback or input you have would be most welcome. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
