scenariotest
This testing helper-class was taken from a gist written by github user ‘bigjason’. It combines a prototypical test case with a list of dictionaries (each a dict of keyword arguments) and transforms the two into a series of unittest-compatible test cases. The advantage of this approach is that an identical test can be applied to multiple scenarios with minimal repetition of code, while still having each scenario tested independently and reported to the user by the test runner.
Example of usage can be found in the file xunit.py, or on bigjason’s blog post which introduced the concept:
<http://www.bigjason.com/blog/scenario-testing-python-unittest/>
The original code this was based off of can be found on GitHub:
<https://gist.github.com/856821/8966346d8e50866eae928ababa86acea6504bcee>
Metadata
Release files for scenariotest 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 |
|---|---|---|---|---|
| scenariotest-1.0.tar.gz | 2.2 kB | Without provenance | Details for scenariotest-1.0.tar.gz |
Release files / scenariotest-1.0.tar.gz
| Download URL | scenariotest-1.0.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aae88b9967cbd55b9b084e236f2fe3198d7b886428e88f51675a206fd44c35a1
|
|
BLAKE2b-256 checksum How to use checksums |
d53266d0ca49708ba058df4bc5905b283e046c13050cf35bb0af1afe1a12e63e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for scenariotest 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.