On Wed, 2007-10-31 at 20:35 +0000, mamcxyz wrote:
> I don't call count manually.
> 
> I'm doing:
> 
> self.assertContains(self.response,u'Fallo el ingreso. Revise su clave
> y usuario')
> 
> assertContains is part of Django Test framework. ie:
> 
>     def assertContains(self, response, text, count=None,
> status_code=200):
>         """
>         Asserts that a response indicates that a page was retreived
>         successfully, (i.e., the HTTP status code was as expected),
> and that
>         ``text`` occurs ``count`` times in the content of the
> response.
>         If ``count`` is None, the count doesn't matter - the assertion
> is true
>         if the text occurs at least once in the response.
>         """
>         self.assertEqual(response.status_code, status_code,
>             "Couldn't retrieve page: Response code was %d (expected
> %d)'" %
>                 (response.status_code, status_code))
>         real_count = response.content.count(text)
> 
> This is where the count is called.

... and so, since you are the one seeing this bug and in a position to
verify if the proposed fix works and then open a ticket if necessary,
the ball is in your court.

Best wishes,
Malcolm

-- 
Many are called, few volunteer. 
http://www.pointy-stick.com/blog/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@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-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to