Skip to main content

django-aftermath

Execute commands after tests are completed.

It requires django-discover-runner package to work.

Usage

Install using pip:

pip install django-aftermath

In your settings file, add the following required options:

TEST_RUNNER = ‘aftermath.AftermathTestRunner’

To specifiy a backend, set a dotted path to the backend class:

AFTERMATH_BACKEND = ‘aftermath.backends.NotifySendBackend’

Currently, there are two backends, NullBackend which does nothing (this is the default), and NotifySendBackend which uses notify-send to generate notifications. You will have to install notify-send yourself.

On Gnome3, NotifySendBackend creates notifications like these:

![notification](notification.png)

To specifiy if backend is executed when all test succeed, use AFTERMATH_RUN_ON_SUCCESS setting. Default values is True.

To specifiy if backend is executed when some tests fail, use AFTERMATH_RUN_ON_FAIL setting. Default values is True.

Usually, you will only need to specify the first two options.

If you wish to implement your own backend, take a look at one of the existing backends. All you need is a simple class with __init__ and aftermath functions. If you make one, I’ll be happy to include it in the package.

TODO

Improve docs/readme.

Metadata

Release files for django-aftermath 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-aftermath 0.1.3
File Size Uploaded Provenance
django-aftermath-0.1.3.tar.gz 3.0 kB Without provenance Details

Release files / django-aftermath-0.1.3.tar.gz

Download URL django-aftermath-0.1.3.tar.gz
Size 3.0 kB
Tags Source
SHA-256 checksum
How to use checksums
320419286ddc864f528f7792e3b6fbece69324dda4886c49b5be76690be40747
BLAKE2b-256 checksum
How to use checksums
7e2e48893d8e55cda9e77a204a5626db2464f8bf58df45f1a7933e2da55bae2a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for django-aftermath 0.1.3

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page