On Sun, 2007-11-18 at 22:54 -0500, Todd O'Bryan wrote: > I've been playing with the Django tests a bit and noticed something > odd. Here's what the docs say: > > Yes, the unit tests need a settings module, but only for database > connection info, with the DATABASE_ENGINE setting. You will also need > a ROOT_URLCONF setting (its value is ignored; it just needs to be > present) and a SITE_ID setting (any non-zero integer value will do) in > order for all the tests to pass. > > If SITE_ID = 1, everything works great. But if SITE_ID = 2 (and, > presumably, other values), I get 6 failures with the final error > message being > > DoesNotExist: Site matching query does not exist. > > My guess is that this isn't what's supposed to happen. Are the docs or > the tests wrong?
Yes. :-) Open a ticket and include the names of the failing tests (the failing test name is included in the first line of the traceback) so that they can easily be found again later. Maybe it's easy to fix, maybe we should just force SITE_ID=1 in runtests.py. Malcolm -- Quantum mechanics: the dreams stuff is made of. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
