pytest-xml
Create simple but detailed XML results for parsing
This pytest plugin was generated with Cookiecutter along with @hackebrot’s cookiecutter-pytest-plugin template.
Features
TODO
Requirements
See requirements.txt
Installation
You can install “pytest-xml” via pip from PyPI:
$ pip install pytest-xml
Usage
TODO
Contributing
Contributions are very welcome. Tests can be run with tox, please ensure the coverage at least stays the same before you submit a pull request.
License
Dual License:
Distributed under the terms of both the BSD-3 AND Mozilla Public License 2.0 licenses.
“pytest-xml” is free and open source software
Issues
If you encounter any problems, please file an issue along with a detailed description.
Metadata
Release files for pytest-xml 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 | Actions |
|---|---|---|---|---|
| pytest_xml-0.1.1.tar.gz | 32.3 kB | With provenance | Details for pytest_xml-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pytest_xml-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for pytest_xml-0.1.1-py3-none-any.whl |
Total release size: 55.8 kB
Release files / pytest_xml-0.1.1.tar.gz
| Download URL | pytest_xml-0.1.1.tar.gz |
|---|---|
| Size | 32.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cbeabc9321f83367e430426fe423806d77abe90c9045bd74ccede7ec418b4aa4
|
|
BLAKE2b-256 checksum How to use checksums |
eb9ddaeae22b39e8826117dfb4a747b10e7bd4b1bde2d1bd2f42e0720f4261a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2024.
Transparency logRelease files / pytest_xml-0.1.1-py3-none-any.whl
| Download URL | pytest_xml-0.1.1-py3-none-any.whl |
|---|---|
| Size | 23.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44f49fd2f86bcfcdd792844762b6a471a4a4a61322143edc074a7af553627ff6
|
|
BLAKE2b-256 checksum How to use checksums |
7b8aa43b34131a027a5b9ec7404bb41f96092e4c6f75d4e8ca44099d6f5e90c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2024.
Transparency logSecurity for pytest-xml 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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pytest_xml-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2024.
Transparency logA 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.