> IMHO, this is a dangerous statement to make - what if one test makes > an (mistaken) change in the database? Then all your subsequent tests [snip]
My application does *not* make any inserts/updates to the database. It merely selects and presents data based on user inputs (application is up here: http://indiawargamers.com/btd/ "cover story" can be found here: http://indiawargamers.com/resources/beat_the_drum.html). Given the (admittedly uncommon) "select only" nature of the app, I think my statement accurately reflects my need. > I would suggest writing (and installing) a custom run_tests method. In > your run_tests implementation, install your fixture, then call the > existing run_tests implementation. > Thanks! I will give this a try. Regards, Manoj --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
