Coverage filter
Allows developers to indicate which code they are trying to test when using coverage tools.
Warning This is just a proof of concept. The API will likely change as I receive feedback. There are also no unit tests, or other code quality control methods in place. If you wish to use this code, please make a copy for yourself, so my changes won’t break your build.
Example
Example code to be tested: (in target.py)
def target(self):
return target_inner()
def target_inner(self):
return 42Example unit test: (in test_target.py)
from coverage_filter import CoverageFilter
from target import target
@CoverageFilter('target.py:target')
def test_target(self):
assert target() == 42For more information, check out my blog on the topic.
1 maintainer
Metadata
1 maintainer
Release files for coverage_filter 0.0.0
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 |
|---|---|---|---|---|
| coverage_filter-0.0.0.tar.gz | 2.7 kB | Without provenance | Details for coverage_filter-0.0.0.tar.gz |
Release files / coverage_filter-0.0.0.tar.gz
| Download URL | coverage_filter-0.0.0.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2740df3908a11471b86adcd652e3f0a164c20dda84d0d7ad4cb0853ed99aebc
|
|
BLAKE2b-256 checksum How to use checksums |
7c7aca44f76768a2c039dfca1c33b534be7572e3aa7e542c275e672869b16c5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for coverage_filter 0.0.0
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.
