On 8/20/07, Viraj Alankar <[EMAIL PROTECTED]> wrote:
> My question is why does my test in polls need to know anything about
> the root url configuration of the project? This seems to couple my
> poll-specific unittest to the project and it would be cleaner to not
> need to specify the '/polls/' url prefix. Also for my test fixture I
> need to specify the 'polls/' subdirectory which also increases that
> coupling.
This is an interesting idea. However, the primary reason is that
fixtures, templates, and other application settings aren't specified
at an application level - they're specified at the project level. As a
result, testing needs to happen at the project level, too.
Essentially, you can't run an application by itself - it needs to have
a project around it, even if only a skeleton project. At the very
least, it's the project that provides the './manage.py test' hook :-)
I'm unclear as to why you need to specify the 'polls' directory in a
fixture, though. There shouldn't be anything project specific in a
fixture file.
> This is probably just a minor nit, but I'm curious if I'm just doing
> this wrong and whether others do it differently. I'm a little confused
> as to how to organize my tests. Placing the unittest files within the
> application directories when they actually require the root url config
> seems strange to me.
Personally, I lean very heavily on reverse URL lookup. In my
applications, I almost never use a literal /foo/bar path, either in
template or view code. Instead, I make sure every URL is named, and I
use reverse() in view code, and {% url %} in templates. This
completely separates the application from the URL - and not just for
testing purposes.
If your application uses URL lookups rather than hard-coding URLs, you
can 'remount' an application anywhere in the URL space without
changing a thing; you can also refactor the URL naming schemes without
having to play games with search and replace.
As a side effect, testing also becomes decoupled - the project in
which the application is mounted becomes irrelevant.
Yours,
Russ Magee %-)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
