Note that there are some explanatory texts on larger screens.

plurals
  1. POPyCharm 1.1 - using specific settings for django test runner
    primarykey
    data
    text
    <p>Does anyone have any experience with using different settings files for the Django test runner in PyCharm?</p> <p>My project is composed as follows:</p> <pre><code>+penguinproject +apps +settings --__init__.py --common.py # this one is imported by the others below --development.py --production.py --staging.py +static ... </code></pre> <p>Running the tests with a manage.py command (and adding --settings=settings.development) works fine, but I'd like to use the built in test runner (as it's better integrated with the IDE).</p> <p>I <em>think</em> the problem is that my settings aren't being loaded correctly, as I get this error:</p> <pre><code>E:\Development\django_projects\penguinproject\Scripts\python.exe "C:\Program Files (x86)\JetBrains\PyCharm 1.1\helpers\pydev\pydevd.py" --client 127.0.0.1 --port 49898 --file "C:\Program Files (x86)\JetBrains\PyCharm 1.1\helpers\pycharm\django_manage.py" test items Testing started at 20:36 ... pydev debugger: warning: psyco not available for speedups (the debugger will still work correctly, but a bit slower) pydev debugger: starting E:\Development\django_projects\penguinproject\lib\site-packages\path.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead import sys, warnings, os, fnmatch, glob, shutil, codecs, md5 settings file: development pycharm django settings imported Manager file: manage Traceback (most recent call last): File "C:\Program Files (x86)\JetBrains\PyCharm 1.1\helpers\pydev\pydevd.py", line 1165, in &lt;module&gt; debugger.run(setup['file'], None, None) File "C:\Program Files (x86)\JetBrains\PyCharm 1.1\helpers\pydev\pydevd.py", line 929, in run execfile(file, globals, locals) #execute the script File "C:\Program Files (x86)\JetBrains\PyCharm 1.1\helpers\pycharm\django_manage.py", line 15, in &lt;module&gt; run_module(manage_file, None, '__main__') File "c:\python26\Lib\runpy.py", line 140, in run_module fname, loader, pkg_name) File "c:\python26\Lib\runpy.py", line 34, in _run_code exec code in run_globals File "E:\Development\django_projects\penguinproject\yabe\manage.py", line 11, in &lt;module&gt; execute_manager(settings) File "E:\Development\django_projects\penguinproject\lib\site-packages\django\core\management\__init__.py", line 438, in execute_manager utility.execute() File "E:\Development\django_projects\penguinproject\lib\site-packages\django\core\management\__init__.py", line 379, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "E:\Development\django_projects\penguinproject\lib\site-packages\django\core\management\base.py", line 191, in run_from_argv self.execute(*args, **options.__dict__) File "E:\Development\django_projects\penguinproject\lib\site-packages\django\core\management\base.py", line 220, in execute output = self.handle(*args, **options) File "E:\Development\django_projects\penguinproject\lib\site-packages\django\core\management\commands\test.py", line 37, in handle failures = test_runner.run_tests(test_labels) File "E:\Development\django_projects\penguinproject\lib\site-packages\django\test\simple.py", line 396, in run_tests suite = self.build_suite(test_labels, extra_tests) File "E:\Development\django_projects\penguinproject\lib\site-packages\django\test\simple.py", line 285, in build_suite app = get_app(label) File "E:\Development\django_projects\penguinproject\lib\site-packages\django\db\models\loading.py", line 140, in get_app raise ImproperlyConfigured("App with label %s could not be found" % app_label) django.core.exceptions.ImproperlyConfigured: App with label items could not be found </code></pre> <p>I don't get this error using manage.py from the command line (also when invoked from within the IDE), which makes me think the development.py settings aren't loaded correctly. Debugging shows that within get_app() (in the loading.py module) settings.INSTALLED_APPS is an empty list.</p> <p>Has anyone succeeded in setting up the test runner with this setup of settings files?</p> <p>Many thanks in advance!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload