I added a new patch to move these two failing tests to regressiontests--where
they get run with the correct settings and pass.
https://code.djangoproject.com/ticket/17327#comment:8
If this isn't the proper place for management command tests like this, I'll
move them to wherever is more appropr
Thanks for catching this. I worked on that patch.
The problem is that those two test cases shouldn't be in the auth tests but
rather somewhere in top-level tests folder (with the other multi DB tests). I'm
not sure exactly where they belong though. If a core dev wants to chime in and
suggest a
Thanks. I stumbled upon the same problem.
On Wednesday, March 7, 2012 4:40:56 PM UTC+8, Ryan Kaskel wrote:
>
> Hi all.
>
> I've pulled in the latest changes and it seems like ticket #17327 [1]
> introduces a few new tests that are raising errors when I run contrib.auth
> tests via my project:
In addition to the above (which I can confirm causes tests to fail in a new
project), I also goofed up a patch related to a different set of auth
tests. I've created #17848 (release blocker) to fix this. [1]
Ticket #16366 [2] required the template context processor cache to be
cleared. The code
Hi all.
I've pulled in the latest changes and it seems like ticket #17327 [1]
introduces a few new tests that are raising errors when I run contrib.auth
tests via my project:
-
auth.MultiDBChangepasswordManagementCommandTestCase.test_that_changepassword_command_with_database_option_uses_given_
