On Aug 27, 1:42 pm, Michael Richardson <[EMAIL PROTECTED]> wrote: > I use > contrib.auth without requiring passwords which invalidates a ton of > urls hooked into contrib.auth.urls - this means that all the tests > fail.
In this case they'd fail irrespective of the templates, 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 contained tests at the expense of the user having to write their own tests for contrib.auth views iff they use them. I guess that applies to contrib.admin too. This is closest to what we have right now (post rev 8497) with the advantage that users without contrib.admin installed will have their project tests pass without having to create an empty app for auth templates. We use test templates and keep them in Django's main test directory. contrib.admin will still require it's own auth view tests as the contrib.auth tests will no longer function as integration tests for admin, and users without contrib.admin installed will still need to supply the templates for their project tests to pass. We use default app templates and keep them in the module: we get self contained tests which also cover user supplied templates (albeit where EN copy changes require translation), but we lose the behavior where the tests fail without a user supplied template. I'll gladly do the work if we can come to decision as to which path to follow. cheers, Cam. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
