nose-quickunit
Given standard test setup, will determine which tests need to run against a given diff.
For example, say you’re working in your branch called my-new-sexy-feature, which modifies the following files:
src/foo/bar/__init__.py src/foo/bar/baz.py src/foo/biz.py
Now if we run with the default options, nosetests --with-quickunit, it will look for tests (by default) in the following base directories:
tests/src/foo/bar/* tests/src/foo/biz/*
(It does this by analyzing the diff against git merge-base HEAD master, and determining which files you’ve changed are tests, including them, and which files containing test coverage in a parallel directory.)
Config
If you want to support multiple directories for searching (let’s say you break up unittests from integration tests) you can do that as well:
--quickunit-prefix=tests/unit/ --quickunit-prefix=tests/integration/
Or, if you’d prefer, via setup.cfg:
quickunit-prefix = tests/unit
tests/integration
Or, via setup.cfg:
quickunit-json = -
1 maintainer
Metadata
1 maintainer
Release files for nose-quickunit 0.5.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 |
|---|---|---|---|---|
| nose-quickunit-0.5.4.tar.gz | 5.2 kB | Without provenance | Details for nose-quickunit-0.5.4.tar.gz |
Release files / nose-quickunit-0.5.4.tar.gz
| Download URL | nose-quickunit-0.5.4.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6134ac087a032f043899bbf2d46f755d1754491d1abda74dafbb0144c7267b86
|
|
BLAKE2b-256 checksum How to use checksums |
515eb84b16ee282ac2f9df39c357feae035dd3f73d8c9cf24a77fd856d5e3377
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for nose-quickunit 0.5.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.
