Introduction
django-jux/JUXD is an attempt to get JUnit-style XML output from the Django test runner. It does a few notable things:
Uses the test runner from the django.utils.unittest abstraction layer (Django >= 1.3 required)
Does not redefine the behavior of the test suite’s run method
Does not redefine the behavior of the test runner’s run_suite method
Includes test suite run time as well as individual test run times
Supports all available unittest2 outcomes (success, failure, error, etc…)
Works with builtin ElementTree to generate the XML output
This job can be done using nose’s xunit plugin, but with the unittest improvements in Python 2.7, my only reason for using nose was for the xunit plugin itself. nose is a bit of a heavy hitter, but it’s a (really good) generic test runner, not django specific. I wanted something a little more targeted, and this is the result.
The main motivator behind this was getting test output into Jenkins CI, which works perfectly.
Installation
Install Django >=1.3 and set up a project. Then, in your django project settings:
# Tell Django to use the JUXD Test Suite Runner TEST_RUNNER = 'juxd.JUXDTestSuiteRunner' # Where to write the output JUXD_FILENAME = '/path/to/junit.xml'
Thanks
This module pulls inspiration from a lot of sources, and credit is due to all of them:
Metadata
Release files for django-jux 1.0.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 | Provenance | |
|---|---|---|---|---|
| django-jux-1.0.2.tar.gz | 4.1 kB | Without provenance | Details |
Release files / django-jux-1.0.2.tar.gz
| Download URL | django-jux-1.0.2.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7572c52a0452072946d6323d377ed1c9bdde80dfdeb0d3b3bcaaa5747fdeb537
|
|
BLAKE2b-256 checksum How to use checksums |
cf62167de933e7ccc172577dc49e03cedfa3fb63ea14b8d63d64572d0b3098ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-jux 1.0.2
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.