id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
22811	Cannot create a settings file that uses both old and new TEST database settings	Tim Graham	Tim Graham	"I'd like to use the following settings on the continuous integration server, but an `ImproperlyConfigured(""Connection default has both NAME and TEST[NAME] specified."")` exception is [https://github.com/django/django/commit/41afae4ce906838fc87d63962104cfb47991f68b#commitcomment-6604478 currently raised].

{{{
# Django <= 1.6
'TEST_NAME': 'test_django_gis_%s_%s' % (PY_VERSION, BUILD_NAME),
# Django 1.7+
'TEST': {
    'NAME': 'test_django_gis_%s_%s' % (PY_VERSION, BUILD_NAME),
},
}}}

I think third-party apps that use multiple versions of Django will also run into this and the need to create a separate settings file seems overkill.

It may be a good idea to remove this constraint and to use simply use `TEST` if defined, ignoring the `TEST_*` values in that case (without warnings so it's possible to silence them)."	Cleanup/optimization	closed	Testing framework	1.7-beta-2	Release blocker	fixed		Shai Berger	Unreviewed	1	0	0	0	0	0