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 TestCas
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 o
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
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
