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 15691 TEST_DEPENDENCIES doesn't use TEST_NAME in circular dependency detection. slinkp@… nobody "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. " Bug closed Testing framework 1.2 Normal worksforme Accepted 1 0 1 0 0 0