Robot Framework support for CoreJet
A work in progress. Has rough edges. Depends on robotsuite.
Is auto-imported by corejet.testrunner >= 1.0.1 just before the generation of CoreJet test report (until a better way for plugins is discovered). Provides IStory-adapter for robotsuite’s RobotTestCase to do the magic.
Generating test skeletons
corejet.robot ships with an XSLT stylesheet for generating test skeletons for Python unittest. If you are using buildout, you can install a helper script for executing the XSLT-transformation with:
[corejet2robot] recipe = zc.recipe.egg eggs = corejet.robot scripts = corejet2robot
And execute it with:
bin/corejet2robot path/to/corejet.xml
Try bin/corejet2robot --help for more information.
Changelog
0.5.0 (2012-07-22)
Fixed to support the latest robotsuite.
Fixed to prepend story level steps into scenarios to allo corejet.testrunner to count them correctly.
0.4.0 (2012-05-31)
Fixed test id and title metadata to default to empty string instead of None.
0.3.0 (2012-05-30)
Fixed the XSLT and the adapter to use ‘Meta: Title’ instead to ‘Meta: Name’ to be more coherent with @story-decorator.
0.1.0 (2012-05-30)
Proof of concept.
Metadata
Release files for corejet.robot 0.5.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.robot-0.5.0.zip | 9.4 kB | Without provenance | Details for corejet.robot-0.5.0.zip |
Release files / corejet.robot-0.5.0.zip
| Download URL | corejet.robot-0.5.0.zip |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07dfe850914e84af082d80a8d4d390a4ad8aee9892e2efea2878e9d46baaf13a
|
|
BLAKE2b-256 checksum How to use checksums |
22bebce9246a0890789bd84faa248e212646d43c98354b4ccccb17774416faa1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for corejet.robot 0.5.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.