Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy Django nose test need --exe?
    primarykey
    data
    text
    <p>Why do I have to use the --exe argument while I run django-nose tests. If I don't use it, it will skip the tests to run</p> <p>e.g.</p> <pre><code>manage.py test myapp Ran 0 tests in 0.000s </code></pre> <p>while my tests are in the correct place etc.</p> <p>Running it in verbosity 3 it shows:</p> <pre><code>nosetests --verbosity 3 myapp </code></pre> <p>it shows: (changed the path names, but anyway, nose finds them but skips them!!)</p> <pre><code>nose.selector: INFO: /path_to_project/path_to_app/myapp/tests.pyc is executable; skipped nose.selector: INFO: /path_to_project/path_to_app/myapp/tests.py~ is executable; skipped </code></pre> <p>The only way to run the tests is using the --exe argument</p> <p>I Am using:</p> <ul> <li>Ubuntu (both 10.4 or 11.4 doesn't matter) </li> <li>Python 2.6 and 2.7 </li> <li>Django 1.4.3</li> </ul> <p>why is that? </p> <p>According to the documents you won't need --exe</p> <p>But after puzzling for a while... and googling and looking here, i got this suggestion.</p> <p>see <a href="https://stackoverflow.com/questions/12867892/nose-doesnt-find-django-tests?">Nose doesn&#39;t find Django tests</a></p> <p>and <a href="https://stackoverflow.com/questions/1457104/nose-unable-to-find-tests-in-ubuntu/">Nose unable to find tests in ubuntu</a></p> <p>But nowhere the explanation of this workaround for what seems to be a bug?</p> <p>Or Am I missing something?</p> <p>I requestion this, because the other questions are quite old, and no satisfactory answer to this problem found.....</p>
    singulars
    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