#15691: TEST_DEPENDENCIES doesn't use TEST_NAME in circular dependency
detection.
-------------------------------+---------------------------
Reporter: slinkp@… | Owner: nobody
Status: new | Milestone:
Component: Testing framework | Version: 1.2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 |
-------------------------------+---------------------------
As far as I can tell, TEST_DEPENDENCIES checks for circular dependencies
by looking at the NAME key, ignoring TEST_NAME if it exists.
This means that if you have some aliases that use the same NAME but
different TEST_NAMEs, it will bail out reporting a circular dependency
even though there isn't one. Example:
{{{
DATABASES = {
'default': {
'NAME': 'mydb',
...
'TEST_NAME': 'test_mydb',
'TEST_DEPENDENCIES': ['users'],
},
'users': {
'NAME': 'mydb',
...
'TEST_NAME': 'test_users',
'TEST_DEPENDENCIES': [],
},
}}}
It's reasonable to ask why you'd have multiple database configs with the
same NAME. On OpenBlock we've been doing that as our default setup,
because most of our dev rigs and deployments use only one physical
database, but when running tests we want to be sure that multi-database
setups work.
--
Ticket URL: <http://code.djangoproject.com/ticket/15691>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en.
