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

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

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

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? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-08-25 19:59 +0100

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

On 25/08/2014 19:36, Skip Montanaro wrote:
>> 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
>

If you wish to write tests using something that can be compiled out 
please don't let me stop you.  Having said that if nose or even nose2 
works for you why not stick with it?  There's also testfixtures, pytest, 
doctest and presumably others.  Horses for courses?

-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence

[toc] | [standalone]

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

csiph-web