FYI, I was finally able to resolve this. I had an assumption that TestCase's began with a freshly created database between TestCase classes. I asserted this in _fixture_setup() and found that assumption to be false. Upon further research I found a setUpClass() in another TestCase that created objects that conflicted with the fixtures loaded in other TestCase classes. Somehow Django-nose's FastFixtureTestCase hid this problem.
What I'm not sure about (and need to investigate) is if Django-nose's TestRunner is the optimizing away fresh databases between TestCase classes, or if that is standard. Rich -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f74ac850-26d4-4db2-8aef-1d595f8279b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
