#7715: admin_tests failures when running Django tests in one natural fashion
---------------------------------------+------------------------------------
Reporter: mtredinnick | Owner: nobody
Status: new | Milestone:
Component: Unit test system | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Comment (by russellm):
Found the problem. All the failures are for tests cases which _should_ be
catching in manage.py itself - the case where you are running manage.py,
but you don't have a settings.py.
If your last comment is accurate (i.e., that your command line reads
'./runtests.py --settings=settings'), then you *do* have a settings file
on your PYTHONPATH - just not the one that the test is testing that you
don't have (if that makes any sense).
If you rename /tests/settings.py to /tests/sqlite.py (and delete
settings.pyc, if it exists) the tests will pass.
The problem is caused by the fact that /tests is in the PYTHONPATH, so
that regressiontests appears as a project directory; however, it may be
possible to put /tests/regressiontests in the PYTHONPATH instead. I'll
have a poke and see what I can do. Worst case, the solution is to document
the fact that you can't use 'settings.py' for your test settings.
--
Ticket URL: <http://code.djangoproject.com/ticket/7715#comment:3>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
