Opened 17 years ago
Closed 17 years ago
#10165 closed (fixed)
Honor TEST_RUNNER setting on runtests.py
| Reported by: | Leo Soto M. | Owned by: | |
|---|---|---|---|
| Component: | Testing framework | Version: | 1.0 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
When running Django on Jython, we like to use a custom test runner to run the Django test suite. Unfortunately, runtests is hardcoded to use the simple runner bundled with Django.
It could be argued that I can always write my own runtests.py, but runtests itself is clearly not API-oriented and at least the whole django_tests function should be duplicated.
The attached patch is quite non-invasive and uses the runner specified on the settings, just as the "test" management command does.
Attachments (1)
Change History (5)
by , 17 years ago
| Attachment: | use_testrunner_setting_on_runtests.diff added |
|---|
comment:1 by , 17 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 17 years ago
| Owner: | removed |
|---|---|
| Status: | assigned → new |
comment:4 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
(In [9918]) Fixed #10165 -- Use settings.TEST_RUNNER in runtests.py
This permits running Django's core tests under an alternative test runner. Most
likely useful to non-CPython implementations, rather than much else (since
Django's core tests might assume things about the test runner).
Patch from Leo Soto.
Seems like a good idea. Marketing as accepted.