Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
From: "Prasad, Ramit" <ramit.prasad@jpmorgan.com>
To: "python-list@python.org" <python-list@python.org>
Subject: RE: assertraises behaviour
Thread-Topic: assertraises behaviour
Thread-Index: AQHNZAe+C+9Y20973EmcJPD96WEAOZctwKJQ
Date: Tue, 17 Jul 2012 17:49:35 +0000
References: <CAF_E5JYANst57yOud+Ot0AbKkePruoCGPUNC5BbyBoMbgaw2_Q@mail.gmail.com> <ju16g6$8o2$1@dough.gmane.org> <CAF_E5JZNrusmb2SziNBOah67ioZG0yf_w5RNJxVVrU8B5Tqzuw@mail.gmail.com> <ju1att$hc4$1@dough.gmane.org> <CAF_E5Ja4kzHGa9vEr5CML5wV7ampCULRRGt=9JtRoqn4Xxummw@mail.gmail.com> <ju1iug$mtd$1@dough.gmane.org> <mailman.2206.1342515998.4697.python-list@python.org> <lmrfd9-he3.ln1@satorlaser.homedns.org>
In-Reply-To: <lmrfd9-he3.ln1@satorlaser.homedns.org>
Accept-Language: en-US
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.2234.1342547396.4697.python-list@python.org>
Lines: 26
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:25521

> > import unittest=0D=0A> >=0D=0A> > class TestWithRaises(unittest=2ETestC=
ase):=0D=0A> >      def test_first(self):=0D=0A> >          assert False=0D=
=0A> >=0D=0A> >      def test_second(self):=0D=0A> >          print("also c=
alled")=0D=0A> >          assert True=0D=0A> >=0D=0A> > if __name__ =3D=3D =
'__main__':=0D=0A> >      unittest=2Emain()=0D=0A> >=0D=0A> > in this case =
also the second test is run even if the first fails=2E=2E=0D=0A> =0D=0A> Th=
e reason for that is that the unit testing framework catches and=0D=0A> han=
dles the error=2E It calls both test functions in some unspecified=0D=0A> o=
rder and logs the result=2E Calls to two separate test functions are=0D=0A>=
 thereby separated from each other=2E This is intentionally so, but I think=
=0D=0A> you can also give the unit testing framework a flag that makes it a=
bort=0D=0A> after the first error=2E In no way will the exception escape fr=
om the=0D=0A> unittest=2Emain() call though, it is all caught and handled i=
nside, also=0D=0A> by intention=2E=0D=0A> =0D=0A> =0D=0A> > But that's prob=
ably easy because we just need to catch exceptions for=0D=0A> > every metho=
d call, so it's not exactly the same thing=2E=2E=0D=0A> =0D=0A> I don't und=
erstand what you want to say here=2E I also don't understand=0D=0A> what yo=
ur problem in general is=2E I guess there are some expectations=0D=0A> whic=
h are not satisfied, but you haven't explained those explicitly yet=2E=0D=
=0A>=0D=0A=0D=0AI think Andrea wants to do the same thing but with nose and=
 not=0D=0Aunittest=2E=0D=0A=0D=0ARamit=0D=0A=0D=0AThis email is confidentia=
l and subject to important disclaimers and=0D=0Aconditions including on off=
ers for the purchase or sale of=0D=0Asecurities, accuracy and completeness =
of information, viruses,=0D=0Aconfidentiality, legal privilege, and legal e=
ntity disclaimers,=0D=0Aavailable at http://www=2Ejpmorgan=2Ecom/pages/disc=
losures/email=2E