skippy-cov
Overview
skippy-cov is a tool that optimizes your Python testing workflow by filtering tests based on code changes. It takes a diff file from git and a .coverage database (generated by coverage.py) to identify and run only the tests relevant to the modified code. This significantly reduces testing time and resources.
Usage
To use this, you first need to generate the following required files:
- Run Coverage Analysis: Generate a
.coveragedatabase usingcoverage.pyviapytest-covwith test contexts
pytest --cov=myproj --cov-context=test myproj/tests/
Then change your code and run
pytest --skippy-cov
In this case, skippy-cov will analyze the changes and run only the tests that are relevant to the modified code.
You can also use skippy-cov as a CLI on its own.
skippy-cov
that will list the tests selected.
Configuration
The inputs for skippy-cov are the coverage file (default: .coverage) and the diff information. By default, the diff is generated in the same way as a pull request (PR) on GitHub: only the changes introduced by your branch compared to the target branch are considered. This is done using the git diff <target>...HEAD (triple-dot) syntax.
You can specify the coverage file and a branch or ref to diff against (e.g., the main branch):
skippy-cov --diff main --coverage-file .coverage
or equivalently
pytest --skippy-cov --skippy-cov-diff main --skippy-cov-coverage-file .coverage
You can also provide a diff file:
git diff > changes.diff
skippy-cov --diff changes.diff --coverage-file .coverage
If you omit the --diff argument, it will default to the main branch as determined by your git remote (usually "main" or "master").
Advanced:
You may pass any valid git diff refspec to --diff, including triple-dot syntax (e.g., main...HEAD or origin/master...feature-branch). If you provide a triple-dot ref, it will be used as-is, giving you full control over the comparison range.
See skippy-cov --help for more information.
Contributing
See CONTRIBUTING.md for information on how to contribute to the project.
License
See LICENSE for licensing information.
Metadata
Release files for skippy-cov 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| skippy_cov-0.2.2.tar.gz | 11.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| skippy_cov-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.7 kB
Release files / skippy_cov-0.2.2.tar.gz
| Download URL | skippy_cov-0.2.2.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c94dd3c12cb046afcac5d416a5934f52fbf9cf900bbfb04f26512958a78b953d
|
|
BLAKE2b-256 checksum How to use checksums |
10672777751785f7955130414c53e27a4fe0ae6e4025a289f21b69546470c224
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 4, 2025.
Transparency logRelease files / skippy_cov-0.2.2-py3-none-any.whl
| Download URL | skippy_cov-0.2.2-py3-none-any.whl |
|---|---|
| Size | 13.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5fdf2418471a85d640064230e63e35fdb9c030c162122d22dcb0a4eb9a02320b
|
|
BLAKE2b-256 checksum How to use checksums |
76c0fa40db4f41e823eb311ee7148f63ed44a85f4b3ec9a11264accd0cc7b41e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 4, 2025.
Transparency log