StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POrunning nose --with-coverage to get all the package files, but not other dependencies and libs
text
Body
copied!<p>My project folder(yeah - I know it's best practice) is something like:</p> <pre><code>. ├── app.py ├── otherscript.py ├── tests/ └── tools/ ├── __init__.py └── toolfile.py </code></pre> <p>I need <code>nose --with-coverage</code> to test the <code>.py</code> scripts in the main folder, <code>tools</code> folder and exclude the <code>tests</code> folder (although I don't really care about excluding that)</p> <p>When I run basic </p> <pre><code>nose --with-coverage </code></pre> <p>I get coverage on all installed dependencies and libs (flask, requests, etc)</p> <p>when I run </p> <pre><code>nose --with-coverage --cover-package=folder name (or . or ./) </code></pre> <p>I get coverage for the tests folder. the <code>tools/__init__.py</code> file and <code>app.py</code> but not for the rest of the scripts:</p> <pre><code>> (opentaba-server) D:\username\pathto\opentaba-server>nosetests --with-coverage -- cover-package=./ ... Name > Stmts Miss Cover Missing > ----------------------------------------------------------------------- Tests\functional_tests\test_return_json 26 0 100% > Tests\unit_test\test_createdb 0 0 100% > Tests\unit_test\test_scrape 0 0 100% app > 63 15 76% 22, 24, 72-81, 8 8-106, 133 tools\__init__ > 0 0 100% > ----------------------------------------------------------------------- TOTAL 89 15 83% > ---------------------------------------------------------------------- Ran 3 tests in 5.182s OK </code></pre> <p>When I run with the <code>--cover-inclusive flag</code> . It just fails with :</p> <pre><code>nosetests-scripts.py: error: no such option: --with-coverage </code></pre> <p>I'll be glad for any help with this</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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