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?
Cheers Benjamin On Thu, Apr 15, 2010 at 10:10, Thomas Guettler <h...@tbz-pariv.de> wrote: > Hi, > > I use django since several months and wrote a lot of > readonly unittests that I run on live systems. > > I think Django has only a infrastructure for test > which use a temporary database. > > I am happy with my solution, but it would be nice > to have the "infrastructure" in django itself. > > - A page to list and start the unittests from a webpage > (Start one, start all of an application, ...) > > - Start the unittest from the shell: > list all unittests, start one, start all of an application. > > Anyone else interested? > > 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 django-us...@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. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
