On Thursday 3 May 2012 at 22:14, Ramiro Morales wrote: > On Thu, May 3, 2012 at 1:29 PM, Andreas Pelme <andr...@pelme.se > (mailto:andr...@pelme.se)> wrote: > > I am trying to run my Django test suite with an alternative test runner > > (py.test), and found some issues with test isolation. > > > > TransactionTestCase does currently not clean up after itself (i.e. flush > > the database), but instead assumes that the next test will flush the > > database. > > [...] > > > > Djangos default testrunner reorders the test suite to run all TestCase > > tests before TransactionTestCases, which avoids this problem. > > Just a quick related note > > There is a [1]proposal to extend this reordering to be: > > * TestCases > * doctests > * TransactionTestCases > > So doctests aren't affected either. > > I intend to commit a fix for it soon. > > -- > Ramiro Morales > > 1. https://code.djangoproject.com/ticket/12408
This won't be an issue if TransactionTestCase resets the database after itself. Andreas -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
