#25415: Django 1.8 regression: tests no longer run checks
-----------------------------------+------------------------------------
Reporter: adamchainz | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by timgraham):
I'm of the opinion that running the system checks as part of the
`manage.py test` command should be opt-in (for example, by writing a test
that asserts the `call_command('check')` output is empty. For example,
when debugging a single test, it doesn't seem necessary to have the
overhead of running `check`. As more options are added to `check` (e.g.
#25500), a default implementation as currently proposed could become
increasing inflexible. I'd like to document the change in the 1.8 release
notes and suggest the alternative.
--
Ticket URL: <https://code.djangoproject.com/ticket/25415#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.9725f4f1781837373ba761f7882136b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
