How to exclude mock package from python coverage report using nosetests
Create a .coveragerc file that excludes what you don't want in the report: http://nedbatchelder.com/code/coverage/config.html
In your .coveragerc move your omit entry from the [report] section to the [run] section.
I had a similar situation testing a series of sub-packages within my main package directory. I was running nosetests from within the top directory of my module and Mock and other libraries were included in the coverage report. I tried using --cover-module my_package in nosetests, but then the subpackages were not included.
Running the following solved my problem:
nosetests --with-coverage --cover-erase --cover-package ../my_packageSo, if all the code that you want to test is in the same directory, then you can get coverage for it alone by specifying the module path to nosetests. This avoids the need to whitelist each of the submodules individually.
(Python 2.7.6, coverage 4.0.3, nose 1.3.7)