Nose plugin that generates a nice html test report with ability of using template based on jinja2 templates from any folder.
Free software: BSD license
Installation
pip install nose-html-reporting
Usage
- --with-html
Enable plugin HtmlOutput: Output test results as pretty html. [NOSE_WITH_HTML]
- --html-file=FILE
Path to html file to store the report in. Default is nosetests.html in the working directory
- --html-report-template=FILE
Path to jinja2 file to get the report template from. Default is templates/report.html from the package working directory
Development
To run the all tests run:
tox
Example
To execute tests:
nosetests tests/test_sample.py --with-html --html-report=nose_report2_test.html --html-report-template=src/nose_htmlreport/templates/report2.jinja2
Changelog
0.1.0 (2015-01-11)
First release on PyPI.
0.2.1 (2015-03-23)
Now plugin catches not only test logging messages, but messages called before test run. Store to separate variable
New report template is default one
Added test run time to context of the report
0.2.3 (2015-08-03)
Added formatting with decoding for test traceback
1 maintainer
Metadata
1 maintainer
Release files for nose-html-reporting 0.2.3
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 | |
|---|---|---|---|---|
| nose-html-reporting-0.2.3.zip | 75.3 kB | Without provenance | Details |
Release files / nose-html-reporting-0.2.3.zip
| Download URL | nose-html-reporting-0.2.3.zip |
|---|---|
| Size | 75.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a17b9e94492bcb6a04e722388c39b73446d3c39e045bf414d63a40e97d9040a
|
|
BLAKE2b-256 checksum How to use checksums |
37e212025b0b211351981468a6cb972f09f67f4192271060c24bb6acb8ea5755
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for nose-html-reporting 0.2.3
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.
