Re: [Django] #7521: auth/tests fail on custom project with "manage.py test"

[Django]

#7521: auth/tests fail on custom project with "manage.py test"
+---
  Reporter:  anonymous  | Owner:  telenieko   
Status:  closed | Milestone:  1.0 
 Component:  Testing framework  |   Version:  1.1-beta-1  
Resolution:  fixed  |  Keywords:  test failure
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by fnl):

 Ok, sorry for adding this into the wrong ticket - moved this issue to
 #8404, as it fits quite well with that description. I think tests that
 force you to use the English language and an overly specific
 implementation schema should not be part of the Django base distribution
 (see my comments there) - however, I am not trying to say "do not run
 tests for installed apps" as suggested by comment:15, what I am arguing is
 that in the base distribution there must be a sensible amount of freedom
 of choice for the implementation, e.g. language and phrase usage
 restrictions made through tests provided by the base distribution are
 misplaced.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7521: auth/tests fail on custom project with "manage.py test"

[Django]

#7521: auth/tests fail on custom project with "manage.py test"
+---
  Reporter:  anonymous  | Owner:  telenieko   
Status:  closed | Milestone:  1.0 
 Component:  Testing framework  |   Version:  1.1-beta-1  
Resolution:  fixed  |  Keywords:  test failure
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

  * status:  reopened => closed
  * resolution:  => fixed

Comment:

 comment:13 seems to be reporting a version of #8404. This ticket has
 already been resolved. If there is a new problem that is not the same as
 #8404 (or some other existing ticket), please open a new ticket so that
 the problem tracking history is straight. Realise that "I do not think the
 tests for an application I have installed should be run at all" is not a
 bug report (comment:14). Improvements welcome; suggestions to now test
 things, not so much. Reclosing.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7521: auth/tests fail on custom project with "manage.py test"

[Django]

#7521: auth/tests fail on custom project with "manage.py test"
+---
  Reporter:  anonymous  | Owner:  telenieko   
Status:  reopened   | Milestone:  1.0 
 Component:  Testing framework  |   Version:  1.1-beta-1  
Resolution: |  Keywords:  test failure
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by fnl):

  * status:  closed => reopened
  * version:  SVN => 1.1-beta-1
  * resolution:  fixed =>

Comment:

 Having the same problems as siddhi. Why are the authentication tests there
 at all, especially, things like self.assert_("Please enter your new
 password" in response.content) should not be part of the base django dango
 distribution, at least not in the beta or stable - I'm having problems to
 test my apps with (1, 1, 0, 'beta', 1) because I always have to first
 remove the useless tests and replace them with something that works for
 me.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7521: auth/tests fail on custom project with "manage.py test"

[Django]

#7521: auth/tests fail on custom project with "manage.py test"
+---
  Reporter:  anonymous  | Owner:  telenieko   
Status:  closed | Milestone:  1.0 
 Component:  Testing framework  |   Version:  SVN 
Resolution:  fixed  |  Keywords:  test failure
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by siddhi):

 There is still a problem here. I have the auth app installed, but I've
 customised the templates. It so happens that the template has a reverse
 lookup to some urls defined in my ROOT_URLCONF. Because the unit test case
 overrides my urls, the reverse lookup fails and the template rendering
 also fails (raises a NoReverseMatch exception) and the unit test fails.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com
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
-~--~~~~--~~--~--~---