Combines Mikhail Korobov’s django-coverage with Jannis Leidel and Carl Meyer’s django-discover-runner.
Usage
One of the objectives of django-discover-runner is to allow separating a Django app’s tests from the code it’s testing. Since tests no longer reside in an app, django-discoverage needs a different way to know which apps to include in the coverage report. It currently collects apps (packages) by looking for an attribute (by default TESTS_APPS) on each TestCase instance in the suite.
For example:
class MyTestCase(TestCase):
TESTS_APPS = ('mycoolapp', 'myproject.anothercoolapp')
...
All modules in the listed apps (except those specified in OMIT_MODULES) will appear in the standard coverage report.
Settings
- APPS_TEST_CASE_ATTR
The attribute django-discoverage looks for on each TestCase instance.
- OMIT_MODULES
Modules not to be traced by coverage. See the coverage API documentation for more details.
TODO
Investigate discovering the apps being tested from the test modules imports (this could be really annoying)
1 maintainer
Metadata
1 maintainer
Release files for django-discoverage 0.2.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 |
|---|---|---|---|---|
| django-discoverage-0.2.1.tar.gz | 3.6 kB | Without provenance | Details for django-discoverage-0.2.1.tar.gz |
Release files / django-discoverage-0.2.1.tar.gz
| Download URL | django-discoverage-0.2.1.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60c28a6fc9fd3dd20a7a0f1013fdb8ae2517f4617ad5122efe094fcce17f21d0
|
|
BLAKE2b-256 checksum How to use checksums |
74cdfcbe61c55094de286abf5af2a2ce688937f528fd93f27ea48115fec1dd22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-discoverage 0.2.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.
