contrib.auth view tests fail if required templates aren't found. This
seems a sensible default in line with Russell's post [1] but rev 8497
introduces a test only template directory [2] which
a) causes the tests to pass in the absence of an actual login template
(the provided template is not a d
On Tue, 2008-08-26 at 18:09 -0700, Cam MacRae wrote:
> contrib.auth view tests fail if required templates aren't found. This
> seems a sensible default in line with Russell's post [1]
The problem with that original position is that it overloads testing to
include both testing the auth app's impl
On Aug 27, 11:20 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> I much prefer self-contained unittests. I read Russell's mail as
> preferring to trade that for installation/configuration testing. I don't
> particularly agree with that, but I could live with it if we decide it's
> the way we
dates a ton of
urls hooked into contrib.auth.urls - this means that all the tests
fail.
I would definitely prefer having self contained templates for
contrib.auth tests - I realize that if templates are to be included by
the users then it's great to have them automatically tested, but
there
mplates, no?
> I would definitely prefer having self contained templates for
> contrib.auth tests*snip*
>
> In other words, my vote is to set up fake templates for the testing.
So if I understand it, to remove the current test dependency on
contrib.admin our options include:
We use
mplates, no?
> I would definitely prefer having self contained templates for
> contrib.auth tests*snip*
> In other words, my vote is to set up fake templates for the testing.
So if I understand it our options include:
We use test templates and keep them in the module: We get self
conta
On Wed, Aug 27, 2008 at 9:20 AM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
>
> On Tue, 2008-08-26 at 18:09 -0700, Cam MacRae wrote:
>> contrib.auth view tests fail if required templates aren't found. This
>> seems a sensible default in line with Russell's post [1]
>
> The problem with that ori
> > There is a middle ground here, which is that those auth-app templates
> > get moved to the Django's main test directory so that they're available
> > only to runtests. That doesn't feel particularly self-contained and
> > again, for me, violates the intuitive meaning of the word unittest, but
Hi All!
After installing django and creating a project runing "django-admin.py
startproject", if I setup a sqlite3 database and try to run the tests
(python manage.py test) it will fail.
Seems that contrib.auth tests are missing 2 template files, making it
dependent of contrib.admin
