[TIP] Test discovery for unittest

holger krekel holger at merlinux.eu
Sat Apr 4 06:09:26 PDT 2009

Hi Michael, 

sorry if my mails came across too negative.  Wasn't meant this way. 

On Sat, Apr 04, 2009 at 13:09 +0100, Michael Foord wrote:
> holger krekel wrote:
>> [...]
>>> One can only hope it will get added to the Python core quickly.
>> Honestly, I don't get why people are eager to add code to
>> python standard lib.  It will take years before one can
>> actually recommend using it and it will not be usable for
>> testing for multiple python versions.  All the large test
>> suites and custom or general test runner out there already have or can 
>> easily provide their own support code.  
>> But i understand that people like the "addCleanup" idea and have
>> used it in their test runner.  Maybe the idea is dead enough to enter 
>> the standard lib. 
>> holger
> And why do they keep developing the language. Honestly its going to be  
> years before anyone gets to use Python 3 for anything practical, what an  
> enormous waste of time...
> You're in a very negative mood Holger, you object in principle to people  
> improving unittest???

I think others did good postings and i agree (and also mailed
so) that the current addCleanup suggestions make some sense to me.
However, in Python voting style i'd say "-0" on it. 

Why? I tried to give background for my views that 

1) unittest.py is maybe not the right place to drive larger scale tests. 

2) improving testing in python is best done outside the standard lib 

The "-0" also signals that none of these remarks is meant to
prevents changes to unittest.py.  I understand and fully respect
that people want to take a pragmatic approach and basically
say: so much test code is using unittest.py style tests so
let's evolve this standard mechanism so that newcomers have a
richer and easier model for writing their tests.  And let's
use a method that several test runners (including py.test, on
a sidenote :) are successfully using.  Hum, maybe i am
actually +0 :)  

hope this clarifies things a bit. 


Metaprogramming, Python, Testing: http://tetamap.wordpress.com
Python, PyPy, pytest contracting: http://merlinux.eu 

More information about the testing-in-python mailing list