On Tue, Feb 17, 2009 at 06:36:56AM -0800, Istvan Albert wrote:
-> > Test running is a little bit clumsy at the moment when you want to run
-> > all of the tests. ?The output is verbose, and it's hard to see failing
-> > tests as they scroll by.
->
-> There are two ways to deal with this, may not be obvious right away.
-> One is to reduce the verbosity
-> with the -v 0 flag, or better yet to run it in strict mode with the -
-> s flag. This latter stops testing at the first error and is the way to
-> run the tests while expecting/fixing errors. We could change the
-> defaults.
I'm not sure what the right default behavior is. Definitely lower
verbosity would be good!
-> > unittest compatibility. ?This could eventually replace runtest, which is
-> > nice but is a bit superfluous in the face of community-supported
-> > frameworks like nose.
->
-> The only pet peeve I have regarding nose is that people end up writing
-> tests that can only be run with nose. Those who know nose well
-> underestimate the overhead of learning nose and forming the proper
-> mental picture of its workings. So there is a tradeoff there, I think
-> there are people who will run fewer tests because of nose. When
-> something happens automatically a large number of people have no idea
-> what is really going behind the scenes and that (over the long term)
-> may end up hurting more than it helps.
I don't disagree. I'm in favor of keeping a simple runtest around, that
simply & clearly runs all of the tests. I think keeping things
unittest-compliant is an OK decision, too. But once runtest starts
acquiring more than two or three options, it acquires complexity that is
not that necessary and is available in nose, Proctor, or py.test.
Or, to put it another way -- we're developing pygr, not a testing
framework, right? ;)
When we get the buildbots running regularly again, I'll make sure to use
runtest and the unittest stuff for test running and code coverage
analysis.
Ooh, and we could make use of the setuptools extension that lets you run
python setup.py test
cheers,
--titus
--
C. Titus Brown, [email protected]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pygr-dev" 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/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
