Introduction
This package provides a buildout recipe based on zc.recipe.testrunner to install a test script for corejet.testrunner.
Usage
In your buildout, add a part like this:
[buildout]
parts =
...
test
...
[test]
recipe = corejet.recipe.testrunner
eggs =
my.package
defaults = ['--auto-color', '--auto-progress']
The recipe accepts the same options as zc.recipe.testrunner, so look at its documentation for details.
When buildout is run, you should have a script in bin/test and a directory parts/test.
To run the tests, use the bin/test script. If you pass the --xml option, test reports will be written to parts/test/testreports directory:
$ bin/test --xml -s my.package
If you are using Hudson, you can now configure the build to publish JUnit test reports for <buildoutdir>/parts/test/testreports/*.xml.
To output a CoreJet report, do:
$ bin/test --corejet="file,path/to/corejet/file.xml" -s my.package
The CoreJet report and output XML file will be placed in parts/test/corejet. You can combine --xml and --corejet.
The example above uses the file CoreJet repository source, which expects to find a CoreJet XML file at the path specified after the comma.
Changelog
1.0.0 (2012-05-26)
Copied recipe from corejet.testrunner to fix the recipe requiring lxml [datakurre]
Metadata
Release files for corejet.recipe.testrunner 1.0.0
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 |
|---|---|---|---|---|
| corejet.recipe.testrunner-1.0.0.zip | 8.6 kB | Without provenance | Details for corejet.recipe.testrunner-1.0.0.zip |
Release files / corejet.recipe.testrunner-1.0.0.zip
| Download URL | corejet.recipe.testrunner-1.0.0.zip |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ea91734c53ddace5a3928d01a33cd27d24eea7211ae3d9582728dd4c9dcbddb
|
|
BLAKE2b-256 checksum How to use checksums |
5b9d0a038852c8ec0ba03089e6b0034db1ad7720729d9db7ad244cd462a4a2b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for corejet.recipe.testrunner 1.0.0
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.