On Fri, Jun 27, 2008 at 4:29 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> El jue, 26-06-2008 a las 06:58 +0800, Russell Keith-Magee escribió:
>> >> My preferred solution here would be to provide a way for test cases to
>> >> substitute a top level URL pattern object for the duration of the
>> >>
El jue, 26-06-2008 a las 06:58 +0800, Russell Keith-Magee escribió:
> >> My preferred solution here would be to provide a way for test cases to
> >> substitute a top level URL pattern object for the duration of the
> >> test. For example:
> >
A patch in these lines is now attached to #7521, the
On Wed, Jun 25, 2008 at 10:40 PM, Gary Wilson Jr. <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee wrote:
>> My preferred solution here would be to provide a way for test cases to
>> substitute a top level URL pattern object for the duration of the
>> test. For example:
>
> Swapping the root
Russell Keith-Magee wrote:
> On Wed, Jun 25, 2008 at 1:17 AM, Marc Fargas <[EMAIL PROTECTED]> wrote:
>> I can think of two options right now:
>>* manage.py test should not run django.contrib.* tests, those are
>> supposed to have been run in runtests.py and working fine (that's the
>>
On Wed, Jun 25, 2008 at 1:17 AM, Marc Fargas <[EMAIL PROTECTED]> wrote:
>
> But oviously, contrib apps should (to not say must) test their views to
> be sure that code released works! Hence, there should be a way for
> contrib apps to have an urls.py and test it.
Agreed. This is something we
Hi all,
You may have noticed that [7716] raised a few bugs around (#7514, #7517
and #7521) the nice one is #7521, which is now marked DDN.
The issue raised by this ticket is that "mange.py test" would fail to
run tests when you had contrib.auth in your INSTALLED_APPS. That is
because [7716]
