Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #77032 > unrolled thread

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

Started bySkip Montanaro <skip@pobox.com>
First post2014-08-26 03:55 -0500
Last post2014-08-26 03:55 -0500
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

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

FromSkip Montanaro <skip@pobox.com>
Date2014-08-26 03:55 -0500
SubjectRe: Switching from nose to unittest2 - how to continue after an error?
Message-ID<mailman.13448.1409043312.18130.python-list@python.org>
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

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web