Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #77032 > unrolled thread
| Started by | Skip Montanaro <skip@pobox.com> |
|---|---|
| First post | 2014-08-26 03:55 -0500 |
| Last post | 2014-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.
Re: Switching from nose to unittest2 - how to continue after an error? Skip Montanaro <skip@pobox.com> - 2014-08-26 03:55 -0500
| From | Skip Montanaro <skip@pobox.com> |
|---|---|
| Date | 2014-08-26 03:55 -0500 |
| Subject | Re: 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
Back to top | Article view | comp.lang.python
csiph-web