pytest-rpc
Extend py.test for RPC OpenStack testing.
Quick Start Guide
Usage
Once installed the plug-in will automatically be loaded by all py.test test runs executed in the Python environment in which the pytest-rpc was installed.
Contributing
See CONTRIBUTING.rst for more details on developing for the “pytest-rpc” project.
Release Process
See release_process.rst for information on the release process for ‘pytest-rpc’
Credits
This Pytest plugin was generated with Cookiecutter along with @hackebrot’s Cookiecutter-pytest-plugin template.
History
1 maintainer
Metadata
1 maintainer
Release files for pytest-rpc 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pytest_rpc-1.1.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for pytest_rpc-1.1.1-py2.py3-none-any.whl |
Release files / pytest_rpc-1.1.1-py2.py3-none-any.whl
| Download URL | pytest_rpc-1.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
cc97b8fb09ce2c9553b153f3b2dccaff79f1c8ac6efd790e084a758d9933f502
|
|
BLAKE2b-256 checksum How to use checksums |
e2390005b686c1ee476d473b7050f57878eabba115a3cb378a797a1adcdf1e4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/2.7.15
|
Security for pytest-rpc 1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
