The Subbehave module exposes Behave step outcomes as commands for consumption by another process. Additional commands are provided for transitions from feature to scenario and from scenario to step. A consumer can provide additional commands for Behave to emit. Behave hooks typically emit these commands to alter the state of the consumer. A Django-testing consumer, Djbehave, was developed in parallel with this module, and it should serve as a model for additional consumers.
Metadata
Release files for subbehave 0.0.1.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 |
|---|---|---|---|---|
| subbehave-0.0.1.0.tar.gz | 8.4 kB | Without provenance | Details for subbehave-0.0.1.0.tar.gz |
Release files / subbehave-0.0.1.0.tar.gz
| Download URL | subbehave-0.0.1.0.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2f276b46e5ba4bee4c04076e5ab3090a8cbca994ce53ad446b758af6de29d336
|
|
BLAKE2b-256 checksum How to use checksums |
e4f19605c43585f322fa9bb108c7feef565fcbf5c32d8da8dd2688bd67ec7446
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for subbehave 0.0.1.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.