My advice to you is to just ignore it all and focus on the tests in your application.
For example, if your app that you wrote yourself is called "amazingapp" then you test only that app thus. --- $ python manage.py test amazingapp --- And it will say something similar to this... --- Creating test database for alias 'default'... . ---------------------------------------------------------------------- Ran 1 test in 0.002s OK Destroying test database for alias 'default'... --- Don't bother testing your framework code or your modules, which Django does if you leave out the app name (assuming you're not making patches for Django itself). PS. Good for you for testing your code. K On Saturday, August 17, 2013 11:27:34 PM UTC-7, Kris Fields wrote: > > Hi, > > The project I'm working on seems to work fine but running "python > manage.py test" results in a lot of failed tests. I'm trying to get a > handle on them but I'm not sure where to start. I'm hoping someone can > help point me in the right direction. > > Most of the failed tests are for django, but some are for mezzanine and > allauth. I've included them all in case it's relevant. > > Running django 1.4.3, python 2.7.2 > Mezzanine 1.4.5, allauth 0.12.0 > > Any help is much appreciated! > > Thanks, > > Kris > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
