Re: Switching from nose to unittest2 - how to continue after an error?

References	<CANc-5UwXqeSbzgBQbWXEvJu-3j1bY+RU76Hz0w36_QaGt+RBaA@mail.gmail.com>
Date	2014-08-25 13:36 -0500
Subject	Re: Switching from nose to unittest2 - how to continue after an error?
From	Skip Montanaro <skip@pobox.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.13428.1408991814.18130.python-list@python.org> (permalink)

Show all headers | View raw

> It appears that unittest in Python 2.7 should be capable enough that I
> can abandon nose in favor of python -m unittest. How do I get it to
> continue past the first failure? The --help output indicates that a -f
> flag causes it to "fail fast", however, that appears to be the
> default. How do I get it to continue after the first failure? FWIW, I
> am using something slightly newer than Python 2.7.5 (built from source
> sometime before 2.7.6 was released).

Ugh... Still no simple test_* functions (everything has to be a method
of a subclass of TestCase)? No support for plain old assert?

*sigh* Never mind...

Skip

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Switching from nose to unittest2 - how to continue after an error? Skip Montanaro <skip@pobox.com> - 2014-08-25 13:36 -0500

csiph-web