[tg-trunk] Re: [patch] Wrap "nosetests" command to "tg-admin tests"

Sun, 24 Sep 2006 11:34:26 -0700

I think lots of people (certainly me, and I know of at least one other for sure :) expect something like running all their tests to be accessible from tg-admin. Until this thread, I certainly didn't know that setup.py was already set up to run nose...

If the concern is that nose will get too "hidden", how does "setup.py tests" not do the same thing?

Would a different name for a tg-admin command be better?
"tg-admin nosetests" perhaps?

Kevin H

On 9/23/06, Kevin Dangoor <[EMAIL PROTECTED]> wrote:

On Sep 22, 2006, at 2:10 PM, [EMAIL PROTECTED] wrote:

>
> I opened a ticket on trac to ask is it good to have a  "tg-admin
> tests"
> command rather than "nosetests" command? (patch with it)
> http://trac.turbogears.org/turbogears/ticket/1120
>
> The PRO is "tg-admin tests" hide the detail of specific test
> framework,
>
> the CON is ?

I actually don't like hiding what we're using *except* for usability
reasons. Hiding the fact that we're using nose just means that it'll
be less obvious for people that Titus Brown's intro to nose is
applicable to stuff they're doing.

Unless tg-admin tests actually somehow makes things work better in
the context of a TG project, I'm -1 on this.

Kevin




--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to