Michael Foord added the comment:

I am concerned that this feature changes the TestResult API in a backwards 
incompatible way. There are (quite a few) custom TestResult  objects that just 
implement the API and don't inherit from TestResult. I'd like to try this new 
code with (for example) the test result provided by the junitxml project and 
see what happens.

I have a broader concern too. I have seen lots of requests for "test 
parameterization" and none *specifically* for sub tests. They are very similar 
mechanisms (with key differences), so I don't think we want *both* in unittest. 
If test parameterization is more powerful / flexible then I would rather see 
that *instead*. 

On the other hand if subtests are *better* then lets have them instead - but 
I'd like to see that discussion happen before we just jump into subtests.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16997>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to