On Mon, Sep 14, 2009 at 6:41 PM, peppergrower < spamcomefindmeple...@gmail.com> wrote:
> > I just started exploring Django's test framework, and it looks like > it'll be fantastic once I get it working. However, while trying to > run a very simple test (just to figure out how to use the test > features), I noticed that the test database that's being created > doesn't contain all of the tables I would expect (i.e., not all of the > ones in the normal database). Since some tables are missing, the > tests don't work. > > I don't know what you mean by "normal database". The test runner essentially does a syncdb on the test database -- thus, it will create all the tables for all the models for all the apps listed in INSTALLED_APPS. If you are seeing behavior different from this we'll need more specifics about what exactly you are doing and what tables, specifically, are missing in order to help figure out what is going on. Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
