On Wed, Nov 30, 2011 at 4:22 PM, Jeremy Dunck <jdu...@gmail.com> wrote: > 1) expand on the testing guide to present fixtures as one option > for test data and point out the options to script fixture generation > or avoiding fixtures in favor of TestCase-called generation, > discussing tradeoffs in the approaches
I would support this. Seems like good documentation to have. > 2) add a django-admin testshell command which would act like > testserver - loading fixtures into a test DB and dropping you into the > shell to munge it as needed; this would be paired with a south feature > for applying migration fixtures. Just to be clear, how would you get the "diff" of what's changed? Would it automatically change the fixture files after you close the shell session? Or would that be up to you? Adrian -- 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.
