#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 | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------
In Django 1.7, 'manage.py test' would run the system checks as part of
'migrate'. This was reliable since at that point the test database[s]
exists. Since #23685 , the `call_command('migrate')` in `create_test_db`
has been skipping the checks and hence no test run calls the checks.
I think the checks should run *somewhere* in the test framework; perhaps
not as part of `migrate`, since there may be multiple databases to set up.
I am manually adding `call_command('check')` to the start of the test
runner's `run_suite` in my project and this works fine.
I found this when upgrading our application, which uses some custom checks
we rely on for developer synchronization on e.g. installed pip packages,
and the checks stopped running.
--
Ticket URL: <https://code.djangoproject.com/ticket/25415>
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/053.59e4e5cb183f22b401c90f27d93a61d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
