pytest-nose-attrib
The pytest-nose-attrib_ plugin serves two purposes. It adds lets to use
nose attribites marks with @attrib decorator. And to pick the tests with
that attribues. It could be usefull when running nose tests with pytest.
Installation
Install the plugin with:
pip install pytest-nose-attrib
Usage examples
To use the plugin, the -a CLI argument has been
provided.
Using pytest-nose-attrib, only tests marked with method='get' can be run using:
$ py.test -a "method=get"
LICENSE
This code falls under the MIT License. Please note that some files or content may be copied from other places and have their own licenses. Dependencies that are being used to generate the databases also have their own licenses.
1 maintainer
Metadata
1 maintainer
Release files for pytest-nose-attrib 0.1.1
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 | |
|---|---|---|---|---|
| pytest-nose-attrib-0.1.1.tar.gz | 3.3 kB | Without provenance | Details |
Release files / pytest-nose-attrib-0.1.1.tar.gz
| Download URL | pytest-nose-attrib-0.1.1.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cefc9279951525138c4c01c17cde299e0a57f5de9e01c57965b432f20bca6995
|
|
BLAKE2b-256 checksum How to use checksums |
e481778ebfe57f89de2ec24208fef0dd549b588c1bdd521165c41a5fb7304170
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Security for pytest-nose-attrib 0.1.1
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.
