qunit and jasmine urlpatterns should be defined only for test

[Akihiro Motoki]

qunit and jasmine urlpatterns are defined in horizon/site_urls.py if settings.DEBUG is True.
DEBUG=True is a valid situation without dev env (it is reasonable when testing).

It is better to use another flag other than DEBUG and define url_pattern "jasmine" and "qunit" only if the new flag is True.

[Julie Pichon (jpichon)]

I'm a bit wary of the proliferation of settings. When setting DEBUG to True, things like the mox dependency only kick in if specifically accessing the jasmine urls so the change is transparent to the user. I wonder what problem adding a new setting will help to solve?

[Akihiro Motoki (amotoki)]

My point is qunit an jasmine urls should not be accessable even when DEBUG is True. Setting DEBUG to True means qunit and jasmine urls are enabled and if it is not blocked a end-user can access the urls. Ideally such URLs are not defined unless it is a test setup. Am I missing something?

[Akihiro Motoki (amotoki)]

I totally forgot the reason why I noticed this bug. I am not sure this needs to be fixed or not.
Additional setting parameter sounds good to me.

[Matt Borland (palecrow)]

Not going to fix this.

Deployments shouldn't put tests in production, and regardless, you must expect some odd behavior if you place a production environment into DEBUG mode. This is also harmless behavior, so I'm not really worried about it.