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

From	Terry Reedy <tjreedy@udel.edu>
Subject	Re: Switching from nose to unittest2 - how to continue after an error?
Date	2014-08-26 12:58 -0400
References	<CANc-5UwXqeSbzgBQbWXEvJu-3j1bY+RU76Hz0w36_QaGt+RBaA@mail.gmail.com> <ltgatu$j7u$1@ger.gmane.org> <CANc-5Ux1pyyhtbeMDXg+2R4f+-mQQOjTjMrXmVB3MAOWOQELhQ@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.13469.1409072308.18130.python-list@python.org> (permalink)

Show all headers | View raw

On 8/26/2014 4:55 AM, Skip Montanaro wrote:
> 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 obviously did not understand your question "How to continue after an 
error?" and still don't.  If you want to be understood, give a snippet 
of code, what happens now, and what you want to happen.

-- 
Terry Jan Reedy

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

Thread

Re: Switching from nose to unittest2 - how to continue after an error? Terry Reedy <tjreedy@udel.edu> - 2014-08-26 12:58 -0400

csiph-web