1.allure标签调整为在用例前运行，2.优化request结果在allure的显示
1 maintainer
Metadata
1 maintainer
Release files for autoTestScheme 0.2.0.37
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 | |
|---|---|---|---|---|
| autoTestScheme-0.2.0.37.tar.gz | 19.7 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autoTestScheme-0.2.0.37-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 59.0 MB
Release files / autoTestScheme-0.2.0.37.tar.gz
| Download URL | autoTestScheme-0.2.0.37.tar.gz |
|---|---|
| Size | 19.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f398f2a08e79c168b978aa1030d9bc06dd0606e4667d7e688392f3e7f5ddd7f9
|
|
BLAKE2b-256 checksum How to use checksums |
f14acdc070246beaca852780cff5e00e212aff55c58eae8636c12af07797d544
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.7
|
Release files / autoTestScheme-0.2.0.37-py3-none-any.whl
| Download URL | autoTestScheme-0.2.0.37-py3-none-any.whl |
|---|---|
| Size | 39.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec56e94b491ca3a2b98f6c02e8407227faaecc4ece501ea2407a767dc013f855
|
|
BLAKE2b-256 checksum How to use checksums |
77611d438c744ca12b186e70ad040fa9fefece3a3c770510652efb80e841ee42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.7
|
Security for autoTestScheme 0.2.0.37
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.
