@gladys, While that didn't solve my original question, it did solve another related problem. Before, I had issue with migrations failing since they depended on pre-existing data (which did not exist in the blank testing database). But if I added an initial_data.json fixture, it gets run for every migration - during prod and testing. This is bad.
So I went with "SOUTH_TESTS_MIGRATE = False", then I manually load the "test_data" fixture during the first test. Works great. I still can't figure out why running "python manage.py test" and running the above code have such different results. I'd love to figure out why, since it would be easier to use the API calls and look in the "failures" var than it is to run the "python manage.py test" command and parse through the output. But for now, the latter gets things working. So thanks! My original question is still open, but I'm un-stuck and can continue working for now. -- 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.
