#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 adamchainz):

 I don't think they should be optional, or if they are, they should be opt-
 out. The checks are a brilliant guard against error, but not running them
 as part of `test` invites them not being run at all in a TDD workflow, as
 often code can be developed with nothing but running the tests. It is also
 surprising that *only* `test` doesn't run them, since every other `manage`
 command does.

 At YPlan we couldn't do without them as part of tests. Our aforementioned
 'installed packages' check saves a lot of time that would otherwise be
 wasted understanding confusing error messages about imports not working,
 and our other custom checks do verification similar to Django's, for
 issues that without resolution it does not make sense to even attempt do
 any tests. Also we don't notice any real overhead, we can still get a
 single test to run in 1 second (with `--keepdb` :) ) despite all our extra
 messing around with `pip freeze` etc.

--
Ticket URL: <https://code.djangoproject.com/ticket/25415#comment:10>
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.78b9d01363f7e3d3a50c866ff9a12d31%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to