There's no Django community standard of which I'm aware for doing this. There *is* a standard way to run tests for Python projects which use setuptools (which yours should do if you want people to be able to `pip install` it) [1].
I usually do something like this blog post describes [2]. Or, you could use this cookie cutter template [3] if you don't want to set it up manually yourself. It's probably the closest thing you'll find to a "standard". [1] http://peak.telecommunity.com/DevCenter/setuptools#test [2] http://joebergantine.com/blog/2015/dec/03/test-reusable-django-application-support-multiple-/ [3] https://github.com/pydanny/cookiecutter-djangopackage On Tuesday, 21 March 2017 09:38:41 UTC+11, th...@copperleaf.com wrote: > > I am working on a Django library (which will be packaged) and want to set > up testing for it. Looking at a number of existing Django libraries, here > seem to be a number of ways to set up testing, and all of them are > different. > > Are there any best practices? Is there a guide that specifies how it > should be done? > > T > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e32424cb-8b12-455e-8f16-f73a850d7c26%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
