On Oct 20, 12:43 pm, "Jorge Vargas" <[EMAIL PROTECTED]> wrote:
> I'm actually -0 on this I think TestController, as well as DBTest
> should be modifiable by the user. for example i got a project where
> we are not running setup-app, so we just replaced the call for
> SetupCommand.
A case like that could be handled by defining your own, project-
specific, TestController in tests/__init__.py, couldn't it?
> the problem you have is that TG is loaded before the application, so
> it can't find the app place. The second problem is that paste config
> demands a full path to the file in place. so the only way I can think
> this could be fix will be to make it a function and call it after the
> app has finish loading.
The problem arises in tg2/tg/tests/test_testutil.py (i.e. the testutil
unit tests in tg2 itself), so there never will be an app to load,
unless one were to mock one before importing anything from testutil.
Put another way, it's a problem with testing the test fixture...
> the reason why I'm not -1 on this is because I think the quickstarted
> project is already way too big and if we could find a way to make it
> smaller (IE, having inheritance to overwrite the defaults, or passing
> in parameters) I'm +1 on that.
Yes, reducing the size and complexity of the quickstart is why I
thought this was a good idea too.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---
