Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
A test runner which can output an XML report compatible with JUnit and Hudson/Jenkins as well as XML and HTML reports compatible with the CoreJet BDD standard
This package provides an extension to the test runner to the one that ships
with zope.testrunner
_.
It is based on (and can be used as a wholesale replacement for),
collective.xmltestreport
.
The test runner is identical to the one in zope.testrunner
, except:
corejet.core
_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 (corejet.recipe.testrunner
) 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.
Other repository sources can be registered via entry points: Packages must
register an entry point under corejet.repositorysource
identifying a
callable that is passed the string after the comma with a unique name and
which should return a corejet.core.model.RequirementsCatalogue
object.
Hence, the file
source is defined as::
def fileSource(path):
catalogue = RequirementsCatalogue()
with open(path) as stream:
catalogue.populate(stream)
return catalogue
and registered with::
[corejet.repositorysource]
file = corejet.testrunner.filesource:fileSource
Use bin/test --help
for a full list of options.
.. _corejet.recipe.testrunner: http://pypi.python.org/pypi/corejet.recipe.testrunner .. _zope.testrunner: http://pypi.python.org/pypi/zope.testrunner .. _zc.recipe.testrunner: http://pypi.python.org/pypi/zc.recipe.testrunner .. _corejet.core: http://pypi.python.org/pypi/corejet.core
Python 2.5 compatibility [jodok]
MANIFEST.in to include CHANGES.txt in sdist [jodok]
FAQs
A test runner which can output an XML report compatible with JUnit and Hudson/Jenkins as well as XML and HTML reports compatible with the CoreJet BDD standard
We found that corejet.testrunner demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.