I'm +1 on moving the contrib tests to tests/<app_label>_tests/ . The respective ticket on Trac is https://code.djangoproject.com/ticket/24293
/Markus On Monday, February 9, 2015 at 4:09:47 PM UTC+1, Tim Graham wrote: > > I wonder if there is any need to continue to ship tests as part of contrib > apps? Currently the contributing docs say, "Tests for contrib apps go in > their respective directories under django/contrib, in a tests.py file. > You can split the tests over multiple modules by using a tests directory > in the normal Python way." but we are currently inconsistent (see below). > Shipping the tests in contrib means that end users may try to run them with > their own projects and this often leads to failures if their project's > settings do not match the settings that runtests.py expects. (e.g. #24299 > asks for us to skip contrib tests that require an 'other' database > connection if a project doesn't have that). > > apps with tests in tests/ > admin > admin_docs > postgres > staticfiles > syndication > > apps with tests in contrib/ > auth > flatpages > gis > humanize > messages > redirects > sessions > sitemaps > sites > > apps with tests in both locations > contenttypes > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/da91fe85-66e9-4122-a4f7-8e99fce770f9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
