Matt Good wrote: > Kevin Horn wrote: >> 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? > > The concern (from my POV) is that setuptools is becoming a Python > standard, so "python setup.py test" should also be a standard way to > run unit tests.
It uses its own test runner, so I think you'd lose features like stdout capturing that nose does. I haven't actually tried, though. That said, you could still separate out the test runner from the test collector, and have the test runner read the test suite from the entry point that setuptools uses. Then, say, "python setup.py nose" could run any test suite with nose, regardless of whether it uses nose as the collector. OTOH, how do you pass arguments to the collector? IMHO setup.py test has an interface that is too limited for a serious user; maybe it is vaguely useful for someone who wants to run tests in a random project that they are only modestly interested in, but I don't think it is currently general enough otherwise. -- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
