Snot is a nose plugin that will allow results from python unit tests to report to Slick.
*OPTIONS:*
–slick-url
the base url of the slick web app [SLICK_URL]
–slick-project-name
the name of the project in slick to use [SLICK_PROJECT_NAME]
–slick-release
the release under which to file the results in slick [SLICK_RELEASE]
–slick-build
the build under which to file the results in slick [SLICK_BUILD]
–slick-build-from-function
get the slick build from a function. The parameter should be the module and function name to call [SLICK_BUILD_FROM_FUNCTION].
–slick-testplan
the testplan under which to file the results in slick [SLICK_TESTPLAN]
–slick-testrun-name
the name of the testrun to create in slick [SLICK_TESTRUN_NAME]
–slick-environment-name
the name of the environment in slick to use in the testrun [SLICK_ENVIRONMENT_NAME]
–slick-testrun-group
the name of the testrun group in slick to add this testrun to (optional) [SLICK_ENVIRONMENT_NAME]
–slick-agent-name
what to put in slick’s hostname field in the result.
–slick-schedule-results
Schedule empty results in slick, but do not run the tests
–slick-schedule-add-requirement
Add a requirement to all results when scheduling.
–slick-schedule-add-attribute
Add an attribute to all results when scheduling.
–slick-schedule-new-requires
apply the requires directly on the result as an attribute.
–slick-testrun-id
Instead of creating a new testrun, use an existing one.
–slick-result-id
Instead of creating a new result in the testrun, update an existing one.
–snot-no-log-capture
Don’t capture the logs from the logging framework
–slick-organize-by-tag
A space delimited list of tag keys to base test run names after. Will be “ - “ delimited.
–slick-sequential-testrun
Use with slick-schedule-results; schedules an entire testrun to be ran in sequence rather than distributed.
–slick-duplicate
Duplicate each test x number of times.
2 maintainers
Metadata
2 maintainers
Release files for slickqa-snot 1.0.2960
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 | |
|---|---|---|---|---|
| slickqa-snot-1.0.2960.tar.gz | 10.6 kB | Without provenance | Details |
Release files / slickqa-snot-1.0.2960.tar.gz
| Download URL | slickqa-snot-1.0.2960.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a6cfe387b8990c0dc748540e3ffa0a3e8b08bdae13e84ed62f5fb5afba90d74
|
|
BLAKE2b-256 checksum How to use checksums |
955b139f3f868d568a8d35b7c939bdf88a4bbf5e2e2a014f29272a2fb6d5c1c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/44.0.0 requests-toolbelt/0.9.1 tqdm/4.42.0 CPython/2.7.15
|
Security for slickqa-snot 1.0.2960
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.
