tha.coverage 0.1

Installation and use

To install, add tha.coverage to a zc.recipe.egg section. You often already have one for common scripts. So something like this:

[buildout]
...
parts =
    ...
    console_scripts

[console_scripts]
recipe = zc.recipe.egg
eggs =
    ...
    tha.coverage

This gives you a bin/createcoverage script that does the following:

• Check whether bin/test exists. Safety feature.

• Remove old coverage dir if it exists. This way you always have clean results.

• Run bin/test with the --coverage=... option.

• Use z3c.coverage to create the actual reports. By default into ./coverage/reports. If you start createcoverage with a command line argument (bin/createcoverage /tmp/output) it will put the reports into that directory.

• Open the reports in your webbrowser if you did not specify an output directory. The assumption here is that if you run the script as-is, you just want to see the coverage reports. If you do specify an output directory, you’re probably running it from within buildbot or so on the server and you want the output in some webserver-served directory. No use to open a browser on the server.

OSX comment

z3c.coverage uses the “enscript” command for python code highlighting. The version provided by OSX complains about an unkown --footer argument passed by z3c.coverage. There are two possible solutions:

• Install enscript from macports.

• Add a script called “enscript” on your path that calls the original enscript minus the offending argument:

  #!/bin/sh
  shift
  /usr/bin/enscript -q --header -h --language=html --color -o - $9

More info

Technical details and a full doctest are in src/tha/coverage/USAGE.txt .

Made by Reinout van Rees at The Health Agency.