Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #77056 > unrolled thread
| Started by | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| First post | 2014-08-26 12:58 -0400 |
| Last post | 2014-08-26 12:58 -0400 |
| 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? Terry Reedy <tjreedy@udel.edu> - 2014-08-26 12:58 -0400
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2014-08-26 12:58 -0400 |
| Subject | Re: Switching from nose to unittest2 - how to continue after an error? |
| Message-ID | <mailman.13469.1409072308.18130.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web