subunitdetails
- Requires:
Python 3.x
python-subunit
testtools
- Author:
Corey Goldberg, 2014
About subunitdetails:
subunitdetails takes a binary encoded subunit stream, and extracts test details (content object attachments) and saves them to the filesystem.
Using subunitdetails to extract content object attachments:
Invoke the subunitdetails script, with a subunit file name as an argument. It will extract the embedded content objects (test details) from the subunit result, into the current directory:
$ subunitdetails <file_name>
About SubUnit:
SubUnit is a streaming protocol for test results. The protocol is a binary encoding that is easily generated and parsed. By design all the components of the protocol conceptually fit into the xUnit TestCase -> TestResult interaction.
About Test Details:
Details are MIME-based content objects that may be attached to a TestCase. This is done using the testtools library (extensions to Python’s standard unittest lib). It allows you to attach any information that you could possibly conceive of to a test, and allows testtools to use or serialize that information.
Using subunit, the encoded stream can be parsed. Test suite results and attached Details (with MIME-types) can then be retrieved.
Installing subunitdetails:
subunit-details uses standard python packaging via setuptools.
There are a few ways to install subunitdetails.
Install from PyPI using pip (system-wide):
$ sudo pip install subunitdetails
Install from PyPI using pip, into a virtualenv::
$ virtualenv -p python3 .env $ source .env/bin/activate $ pip install subunitdetails
Clone the dev repository and install, using a virtualenv:
$ git clone https://github.com/cgoldberg/subunitdetails.git $ cd subunitdetails $ virtualenv -p python3 .env $ source .env/bin/activate $ python3 setup install
Metadata
Release files for subunitdetails 0.0.4
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 |
|---|---|---|---|---|
| subunitdetails-0.0.4.tar.gz | 3.6 kB | Without provenance | Details for subunitdetails-0.0.4.tar.gz |
Release files / subunitdetails-0.0.4.tar.gz
| Download URL | subunitdetails-0.0.4.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d964f90849cfa75a8a740a32fc8eaaa57af2c18cea9c036201d0a8903afab807
|
|
BLAKE2b-256 checksum How to use checksums |
a947b97db5bb8f01d35cd6e3eec6c61e2454b01cc6f888627c5052064b8b8d19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for subunitdetails 0.0.4
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.