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


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

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

Started bySkip Montanaro <skip@pobox.com>
First post2014-08-25 13:36 -0500
Last post2014-08-25 13:36 -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-25 13:36 -0500

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

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

[toc] | [standalone]


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


csiph-web