
Security News
Software Engineering Daily Podcast: Feross on AI, Open Source, and Supply Chain Risk
Socket CEO Feross Aboukhadijeh joins Software Engineering Daily to discuss modern software supply chain attacks and rising AI-driven security risks.
createcoverage
Advanced tools
.. image:: https://travis-ci.org/reinout/createcoverage.svg :target: https://travis-ci.org/reinout/createcoverage
.. image:: https://coveralls.io/repos/reinout/createcoverage/badge.svg?branch=master&service=github :target: https://coveralls.io/github/reinout/createcoverage?branch=master
This package installs one command: createcoverage that runs your tests
with coverage.py and opens the coverage reports in your browser. All with
just one single handy command.
Assumption: you're using buildout. Or rather, the assumption is that you have
a bin/test command that runs all your tests.
No options are passed to coverage.py, so any extra options you want to give to
coverage must be put in a .coveragerc in your buildout's root. This is a
good idea in any case :-) An example .coveragerc that omits code you normally
don't want to include in a coverage report::
[report]
omit =
/home/*/.buildout/eggs/*
/usr/*
parts/*
eggs/*
*/test*
Installing createcoverage in a zc.recipe.egg section is enough.
Createcoverage itself depends on coverage.py <http://nedbatchelder.com/code/coverage/>_ and makes sure bin/coverage is
created::
[console_scripts]
recipe = zc.recipe.egg
eggs = createcoverage
The code is hosted at github: https://github.com/reinout/createcoverage .
You can also report issues and bugs and ideas <https://github.com/reinout/createcoverage/issues>_ there. Pull
requests are of course also very welcome :-)
The first time, you'll have to run the "bootstrap" script to set up setuptools and buildout::
$ python bootstrap.py
And then run buildout to set everything up::
$ bin/buildout
(On windows it is called bin\buildout.exe).
You'll have to re-run buildout when you or someone else made a change in
setup.py or buildout.cfg.
The current package is installed as a "development package", so
changes in .py files are automatically available (just like with python setup.py develop).
Tests can always be run with bin/test or bin\test.exe.
Created by Reinout van Rees <http://reinout.vanrees.org>_.
bin/coverage script (it pointed at an old entry point). Note that
this script is only included because buildout originally didn't install
scripts of dependencies. It does now, with the proper configuration. But
installing this script ourselves solves every case.Note: no functional changes in this release.
Moved to github: https://github.com/reinout/createcoverage .
Noted (in the setup.py classifiers) that we work just fine with
python 3!
Set up travis testing and coveralls.io integration. 100% coverage, of course :-)
-t/--test-args command line option. The string passed to
that is passed straight on to the test runner. For instance, use
-t "-m somemodule" to effectively run bin/test -m somemodule. Note the need for quotes (single or double) as you're
using an option to pass options... Fix by Godefroid Chapelle,
thanks!index.html file on OS X when
using Python 2.7 or newer by using a file URL instead of a path.bin/coverage.First working version.
Copied some code from the "createzopecoverage" package.
Initial library skeleton created by nensskel. [reinout]
FAQs
Single command to create coverage reports (assumes a bin/test)
We found that createcoverage demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Socket CEO Feross Aboukhadijeh joins Software Engineering Daily to discuss modern software supply chain attacks and rising AI-driven security risks.

Security News
GitHub has revoked npm classic tokens for publishing; maintainers must migrate, but OpenJS warns OIDC trusted publishing still has risky gaps for critical projects.

Security News
Rust’s crates.io team is advancing an RFC to add a Security tab that surfaces RustSec vulnerability and unsoundness advisories directly on crate pages.