#17032: Tests for contrib.auth fail if login signals use templates
-------------------------------------+-------------------------------------
     Reporter:  jMyles               |                    Owner:  jMyles
         Type:  Bug                  |                   Status:  reopened
    Component:  Testing framework    |                  Version:  1.3
     Severity:  Normal               |               Resolution:
     Keywords:  contrib.auth, tests  |             Triage Stage:  Design
    Has patch:  1                    |  decision needed
  Needs tests:  0                    |      Needs documentation:  0
Easy pickings:  0                    |  Patch needs improvement:  0
                                     |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by julien):

 For the record, I think this is just a symptom of a deeper problem, i.e.
 that Django doesn't provide a clean environment for unit tests to be run
 in. Other examples of such symptomatic issues are: #17194, #13394, #16366,
 #10976, #8404, #16413, and many more. Whatever we do to fix those symptoms
 we will always keep finding more and more of them — this just has no end
 as it's impossible to predict all the combinations of settings people
 might use in the wild with their projects. Patching those tests with
 little fixes does make them more isolated, but it also does make the tests
 harder to read as it increases the amount of boilerplate code inside the
 tests, without doing anything really useful like increasing the code
 coverage or fixing actual bugs in the tested code.

 As stated earlier in this thread, I see no reason for running the Django
 contrib apps from one's project with '`manage.py test`' at all. Those
 tests are already run by the CI server, and running them from your project
 will add no value to you. They can only cause annoyances when they fail
 because of isolation problems. This is why I recommend to simply ignore
 those tests and not run them from your project.

 I contend that our energy would be better spent focusing on finding a more
 general solution to the root cause. I don't think much work has been done
 in that area yet. I know at least of #9156 addresses that.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17032#comment:7>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to