Buildout recipe to create a zope.testing test runner
The recipe supports the following options:
The eggs option specified a list of eggs to test given as one ore more setuptools requirement strings. Each string must be given on a separate line.
The script option gives the name of the script to generate, in the buildout bin directory. Of the option isn’t used, the part name will be used.
One or more extra paths to include in the generated test script.
The defaults option lets you specify testrunner default options.
The working-directory option lets to specify a directory where the tests will run. The testrunner will change to this directory when run. If the working directory is the empty string or not specified at all, the recipe will create a working directory among the parts.
A set of environment variables that should be exported before starting the tests.
Provide initialization code to run before running tests.
Use egg, test, and working-directory paths relative to the test script.
This is a minimal ‘’buildout.cfg’’ file which creates a test runner:
[test] recipe = tranchitella.recipe.testrunner eggs = myapplication [test-coverage] recipe = tranchitella.recipe.testrunner eggs = myapplication defaults = ['--coverage-module', 'myapplication', '--coverage-branch']
- Updated code to depend on zope.testrunner instead of zope.testing.
- Added a new option (–coverage-html) to run the html coverage command.
- Added a new option (–coverage-annotate) to run the annotate coverage command.
- Added a new option (–coverage-xml) to run the xml_report coverage command.
- First release, forked from zc.recipe.testrunner.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size tranchitella.recipe.testrunner-0.4.tar.gz (15.5 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for tranchitella.recipe.testrunner-0.4.tar.gz