A simple plugin that combines test times and test setup times and writes the output to JSON files. I ripped most of this out of nose-congestion:
https://github.com/acdha/nose-congestion
And added in a few bits for my own needs.
This is a work in progress to do what I want and not much more at this point.
Usage
To install:
pip install nose-timing
When running your tests add:
--with-timing
To get your timing to run. By default it will write to your current directory two files, setup.json and tests.json. To alter where it writes to:
--output-directory=/tmp
1 maintainer
Metadata
1 maintainer
Release files for nose-timing 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 |
|---|---|---|---|---|
| nose-timing-0.1.1.tar.gz | 2.9 kB | Without provenance | Details for nose-timing-0.1.1.tar.gz |
Release files / nose-timing-0.1.1.tar.gz
| Download URL | nose-timing-0.1.1.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc8af5a573fb869e6f6b028ff40587a6810c216b582a9ea3583fd1158b1eb2d2
|
|
BLAKE2b-256 checksum How to use checksums |
0beab40c226ddafc1037c3eb2928b6094eb18d48d4d8dc08a097c05e822b497e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for nose-timing 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.
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.
