pytest-dirty
Static import analysis for thrifty testing.
Overview
With pytest>=8.2 and git, one can easily find what Python files have been
changed and what test files to run.
# 1. List files changed in a pull request.
git diff --name-only main..<pr-branch> > changed.txt
# 2. Run `pytest-dirty` to know what chaned files of package `<package>` affect
tests in `tests` directory must be run.
pytest-dirty -s <package> -t tests changed.txt > affected.txt
# 3. Run tests with pytest.
pytest -s -vv @affected.txt
Metadata
Release files for pytest-dirty 0.0.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 |
|---|---|---|---|---|
| pytest_dirty-0.0.1.tar.gz | 12.5 kB | Without provenance | Details for pytest_dirty-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pytest_dirty-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for pytest_dirty-0.0.1-py3-none-any.whl |
Total release size: 22.4 kB
Release files / pytest_dirty-0.0.1.tar.gz
| Download URL | pytest_dirty-0.0.1.tar.gz |
|---|---|
| Size | 12.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b0d51696e5233fe87badb9c1853b749c5f71bd956cbdec5853880693050d386
|
|
BLAKE2b-256 checksum How to use checksums |
a7b14f7bb9fe3b11f2854f21797b41d7272b4fed4f2a1c3034f1eec7fc38d5fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / pytest_dirty-0.0.1-py3-none-any.whl
| Download URL | pytest_dirty-0.0.1-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
572add8ba68815967291f2df1c0241cd099b3571dd0174013cf57b3a9d7edd9e
|
|
BLAKE2b-256 checksum How to use checksums |
677de14fe797803754357eea5262de1612b62b972c7f934a689ca1b31840c741
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for pytest-dirty 0.0.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.