This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description


In case this is not clear enough: this module is a joke ! Do not use it. It is not dangerous; it is just useless.

Nowadays, every trendy project has a collection of shiny littel badges. They look great, but they can be hard to get. This modules is here to help you to get the 100 % test coverage badge, without any effort.

What’s new?

See changelog.

Download and install

  • From sources:

  • From pip:

    pip install fullcoverage
  • Quick and dirty Debian (and Ubuntu?) package

    This requires stdeb to be installed:

    python3 --command-packages=stdeb.command bdist_deb
    sudo dpkg -i deb_dist/fullcoverage-<VERSION>_all.deb


Let’s say you want to get you module foobar thoroughly covered.

  1. Install fullcoverage:

    pip install fullcoverage
  2. Enable this plugin. That is, in the .coveragerc file of foobar, have the lines:

    plugins = fullcoverage.plugin
  3. Optionnaly, if you want to restrict the test report to your module, you can add, in the same .coveragerc file:

    source = foobar
  4. If you already have tests that import all of foobar submodules, that’s it. Otherwise, somewhere in your tests, have the following lines import everything in your module:

    import foobar
    import fullcoverage
  5. That’s it! You can now run your tests:

    coverage run --source foobar -m unittest
    coverage report --fail-under=100

Bugs and Limitations

  • This does not work with doctest. Please feel free to send a patch.
  • This only works with python 3.5. Please feel free to send a patch.
  • Even though tests cover 100 % of your module, it may still contain bugs.


  • Isn’t it dangerous? Are you running every line of a module to get 100 % test coverage? What if you run a line shutil.rmtree('/') ?

This plugins does not run random line of codes. It imports every plugin that is to be covered, but it cheats coverage into thinking they were thoroughly tested, without testing anything. If your module is safe to import, it is safe to use fullcoverage. If your module is not safe to import, fix your module.

  • If your plugin is so great, why aren’t you showing off with one of those 100 % coverage badges?

Well, fullcoverage is hosted on a Gitlab instance, which does not provide those badges yet. But this plugin is implemented to test itself, and it is thoroughly covered by tests.

Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
fullcoverage-0.1.0-py3-none-any.whl (8.5 kB) Copy SHA256 Checksum SHA256 py3 Wheel Mar 24, 2016
fullcoverage-0.1.0.tar.gz (24.9 kB) Copy SHA256 Checksum SHA256 Source Mar 24, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting