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

References	<CANc-5UwXqeSbzgBQbWXEvJu-3j1bY+RU76Hz0w36_QaGt+RBaA@mail.gmail.com> <ltgatu$j7u$1@ger.gmane.org>
Date	2014-08-26 03:55 -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.13448.1409043312.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Mon, Aug 25, 2014 at 4:47 PM, Terry Reedy <tjreedy@udel.edu> wrote:
> I know of two ways to collect multiple failures within a test function:

Thanks, but I mean multiple test failures. I fully expect a specific
test to exit when it hits an assertion failure.

I suspect my problem is due to lack of support for the assert
statement by unittest. I'll just go back to nose1 for now.

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-26 03:55 -0500

csiph-web