On Thu, Jul 16, 2015 at 8:18 AM, Roland Swingler <roland.swing...@gmail.com> wrote: > I understand that the test db uses a different schema (it's the same in > rails), the point is to be able to run tests isolated from having a database > at all.
there are several testing styles, each one with different dogmas. discussions of the adequacy of them can get very heated and non-productive. one of these styles states that each test should be perfectly isolated from any other conceivable source of errors, including the database, and in fact stopping short of suspecting the base OS itself (usually). without trying to get too deep in religious dogma, i'll just say that Django tests don't favor too much into the "unit" test spectrum; instead they lean somewhat towards the "integration" camp (although not totally there, either). in short, the database is considered a required infrastructure service, and tests usually assume it works as expected. -- Javier -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFkDaoR08cr5DSFH9HOXXxXvdH2QwefE-xuO0yi8hDmf58bSNg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
