Bazinga
Bazinga is a nose plugin to run incremental tests.
Motivation
Running the complete test suite on large projects can take a significantly large time. This can affect your work flow, specially if you are doing TDD. Some people choose to run only a subset of the tests, specifying them explicitly on the command line, but you can easily forget to run affected tests after any particular change and things can break unnoticed. Using “bazinga” you can rest assured that all (and only) the affected tests will be run.
How it works
Inspecting what is imported by each module, “bazinga” recursively detects what are the dependencies for each test. Only tests that failed, were modified, or had a file that they depend on changed, are run. Each time nose is run with bazinga, a md5 hash for each module that your project depends on will be stored on a file named .nosebazinga on the working directory. This file also contains a dependency graph that is used as cache. Bazinga will run all the tests that are needed if a third party package is updated, but the standard library is considered “stable” and is not checked for modifications.
Installation
pip install Bazinga
Usage
nosetests --with-bazinga
Debugging
nosetests --with-bazinga --debug=bazinga
Requirements
Nose
Snakefood
LICENSE
MIT License
Metadata
Release files for Bazinga 0.2.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 |
|---|---|---|---|---|
| Bazinga-0.2.4.tar.gz | 3.6 kB | Without provenance | Details for Bazinga-0.2.4.tar.gz |
Release files / Bazinga-0.2.4.tar.gz
| Download URL | Bazinga-0.2.4.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcb59d4e3fc23c3c8805cf9e97b6cb5cf79e19f61da3d45443c0ef7c745dd30a
|
|
BLAKE2b-256 checksum How to use checksums |
233e3a456438692d04082a1c6be508d4047d1618d18a18daa6164a81081b2903
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Bazinga 0.2.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.