tranchitella.recipe.testrunner
This recipe creates a zope.testing test runner script which supports code coverage analysis using the coverage python library.
Usage
The recipe supports the following options:
eggs
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.
script-name
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.
extra-paths
One or more extra paths to include in the generated test script.
defaults
The defaults option lets you specify testrunner default options.
working-directory
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.
environment
A set of environment variables that should be exported before starting the tests.
initialization
Provide initialization code to run before running tests.
relative-paths
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']
Changes
0.4 (2010-08-24)
Updated code to depend on zope.testrunner instead of zope.testing.
0.3 (2010-06-14)
Added a new option (–coverage-html) to run the html coverage command.
0.2 (2010-04-22)
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.
0.1 (2010-04-22)
First release, forked from zc.recipe.testrunner.
Metadata
Release files for tranchitella.recipe.testrunner 0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tranchitella.recipe.testrunner-0.4.tar.gz | 15.5 kB | Without provenance | Details for tranchitella.recipe.testrunner-0.4.tar.gz |
Release files / tranchitella.recipe.testrunner-0.4.tar.gz
| Download URL | tranchitella.recipe.testrunner-0.4.tar.gz |
|---|---|
| Size | 15.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5fa52be7b30748838e1e7c037fde346fd578e1f5c5ab159a663cf9092d8fbd9
|
|
BLAKE2b-256 checksum How to use checksums |
9a6195954b0e8aeb2a49e0547c0e602b02b6a9f78c59f433e6250431d7b070d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tranchitella.recipe.testrunner 0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.