Ended up populating the test database with fixtures via .json dumps. Thank you very much for your help.
--- Chris On Oct 26, 6:19 pm, Karen Tracey <kmtra...@gmail.com> wrote: > On Mon, Oct 26, 2009 at 4:12 PM, Chris Allen <callen.2...@gmail.com> wrote: > > > Anyone have any experience with forms (ModelMultipleChoice fields and > > foreignkey'd choice fields) not validating properly in a unit test but > > just fine in the runserver? > > > Passing the same request.POST data to the unit test as I am in the > > runserver and live instance, which I verified via the debugger. > > Runserver uses your development database, test uses an initially empty test > database. You've got primary key id values hardcoded in your test data. You > don't say anything about how you are ensuring that the test database has > exactly the same data, including primary key values, as your development > one. Are you doing something that would make this assumption that the > development and test databases are identical valid? Because it's not, in > general. > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
