ZC Buildout recipe for creating CoreJet test runners
Project description
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]
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Hashes for corejet.recipe.testrunner-1.0.0.zip
Algorithm | Hash digest | |
---|---|---|
SHA256 | 9ea91734c53ddace5a3928d01a33cd27d24eea7211ae3d9582728dd4c9dcbddb |
|
MD5 | d908e6463f486a14543f7e3345b6e34e |
|
BLAKE2b-256 | 5b9d0a038852c8ec0ba03089e6b0034db1ad7720729d9db7ad244cd462a4a2b5 |