This problem exists both in master and stable/1.6.x (I didn't check
earlier versions).
The tests pass only when they're run in combination with the
model_inheritance tests.
{{{
tests % ./runtests.py model_inheritance_same_model_name model_inheritance
--settings=test_sqlite
Creating test database for alias 'default'...
Creating test database for alias 'other'...
........
----------------------------------------------------------------------
Ran 8 tests in 0.053s
OK
Destroying test database for alias 'default'...
Destroying test database for alias 'other'...
}}}
It would be useful to fix this because it can create false positives when
using the --bisect or --pair options of the test suite.
--
Ticket URL: <https://code.djangoproject.com/ticket/21671>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/21671#comment:1>
Comment (by claudep):
Would it be acceptable that those tests are skipped when
`model_inheritance` app is not tested/installed (as of attached patch)?
--
Ticket URL: <https://code.djangoproject.com/ticket/21671#comment:2>
Comment (by aaugustin):
That's a reasonable solution.
We have an API to tell if an application is installed in Django 1.7:
https://docs.djangoproject.com/en/dev/ref/applications/#django.apps.apps.is_installed
--
Ticket URL: <https://code.djangoproject.com/ticket/21671#comment:3>
* cc: anubhav9042@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/21671#comment:4>
* status: new => closed
* resolution: => fixed
Comment:
Fixed in #22402 (the `model_inheritance_same_model_name` app was
consolidated into `model_inheritance`).
--
Ticket URL: <https://code.djangoproject.com/ticket/21671#comment:5>