[issue1466] Special reporting of NotImplementedError in unittest

Erik Andersén added the comment: No, I definitely don't want to ignore them, I want them reported in a manner that is relevant to them. Just say that the test was not implemented. No tracebacks for debugging since there is nothing to debug. In addition to a TestRunner I need a new TestCase and

[issue1466] Special reporting of NotImplementedError in unittest

Guido van Rossum added the comment: Sorry Erik, but I don't think you should try to compensate for your flawed methodology by trying to change the unittest framework. End of discussion. __ Tracker <[EMAIL PROTECTED]>

[issue1466] Special reporting of NotImplementedError in unittest

Raghuram Devarakonda added the comment: > Possible, but cumbersome. You have to analyze each case and see if it Have you tried to write a Test Runner that ignores NotImplementedError? You may have to override TestResult.addError. __ Tracker <[EMAIL PROTECTED]>

[issue1466] Special reporting of NotImplementedError in unittest

Erik Andersén added the comment: Possible, but cumbersome. You have to analyze each case and see if it depends on code not written. When you implement a new piece of code, you have to go through all your tests to see if that one should be included. Also you don't get any reporting on the covera

[issue1466] Special reporting of NotImplementedError in unittest

Guido van Rossum added the comment: Sorry, just comment out those tests until you're ready to write the code. __ Tracker <[EMAIL PROTECTED]> __ ___ Pytho

[issue1466] Special reporting of NotImplementedError in unittest

Erik Andersén added the comment: Raghuram Devarakonda skrev: > Raghuram Devarakonda added the comment: > > I don't think unittest automatically treats all exceptions as failures. > Failures are those that are explicitly flagged with assert* and fail* > methods. All other exceptions result in "err

[issue1466] Special reporting of NotImplementedError in unittest

Raghuram Devarakonda added the comment: I don't think unittest automatically treats all exceptions as failures. Failures are those that are explicitly flagged with assert* and fail* methods. All other exceptions result in "errors". I think what you are asking for is to special case one such error

[issue1466] Special reporting of NotImplementedError in unittest

Guido van Rossum added the comment: No. If you're testing something that's not implemented, it is correct to see that as a failure. Talk to anyone doing TDD. -- nosy: +gvanrossum resolution: -> wont fix status: open -> closed __ Tracker <[EMAIL PROTECTED

[issue1466] Special reporting of NotImplementedError in unittest

New submission from Erik Andersén: When a unittest test case raises an Exception, that test case is considered a failure. However, raising NotImplementedError is not a failure. It is something completely normal during development and simply indicates that the functionality has not yet been imple