pytest-result-log
摘要
pytest-result-log是一个在日志文件中记录每个用例的开始、结束和结果信息的pytest插件。
预览
pytest-result-log是sanmu框架孵化的第三个pytest插件,
通过hook钩子的方式,可以准确判断所有类型的用例执行结果,并记录到日志文件中,效果如下
安装
执行命令
pip install pytest-result-log
启用
修改配置文件pyetst.ini
[pytest]
log_file = pytest.log
log_file_level = info
log_file_format = %(levelname)-8s %(asctime)s [%(name)s:%(lineno)s] : %(message)s
log_file_date_format = %Y-%m-%d %H:%M:%S
文档
Metadata
Release files for pytest-result-log 1.2.2
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_result_log-1.2.2-py3-none-any.whl | Python 3 | none | any | Details for pytest_result_log-1.2.2-py3-none-any.whl |
Release files / pytest_result_log-1.2.2-py3-none-any.whl
| Download URL | pytest_result_log-1.2.2-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
147b363113812825da817d799c76e1b0f20a772ae8efaf9f4c08558ca79c1067
|
|
BLAKE2b-256 checksum How to use checksums |
dd9326dbbbb57634fde9cf0bf960506fd3d2ee9eb37d4f0fd6cf4f635f88a8ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Security for pytest-result-log 1.2.2
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.