Benjamin Reitzammer wrote: > Hi Thomas, > how did you make sure, that the tests are read-only? Did you apply any > special measures/tricks (like using a special DJANGO_SETTINGS_MODULE, > that has read-ony access to the database), or are your tests read-only > by convention and you trust the developer that he/she does the > RightThing?
Hi, yes, I trust me and my co workers. But I have a "allways rollback" decorator, too. But unittest writers need to use it explicitly. It is not applied automatically. But you are right. Maybe the unittest should redefine methods which modify the DB, that an exception gets raised. And there are some other features: Call all views, except views which have the attribute 'no_readoly_test' with a pseudo GET request. I run this script nightly and after updates. Thomas -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
