Path: csiph.com!usenet.pasdenom.info!gegeweb.org!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
To: python-list@python.org
From: Mark Lawrence <breamoreboy@yahoo.co.uk>
Subject: Re: assertraises behaviour
Date: Tue, 17 Jul 2012 19:03:19 +0100
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> <5B80DD153D7D744689F57F4FB69AF4741657AA3F@SCACMX008.exchad.jpmchase.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
In-Reply-To: <5B80DD153D7D744689F57F4FB69AF4741657AA3F@SCACMX008.exchad.jpmchase.net>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.2240.1342548197.4697.python-list@python.org>
Lines: 58
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:25527

On 17/07/2012 18:49, Prasad, Ramit wrote:
>>> import unittest
>>>
>>> class TestWithRaises(unittest.TestCase):
>>>       def test_first(self):
>>>           assert False
>>>
>>>       def test_second(self):
>>>           print("also called")
>>>           assert True
>>>
>>> if __name__ == '__main__':
>>>       unittest.main()
>>>
>>> in this case also the second test is run even if the first fails..
>>
>> The reason for that is that the unit testing framework catches and
>> handles the error. It calls both test functions in some unspecified
>> order and logs the result. Calls to two separate test functions are
>> thereby separated from each other. This is intentionally so, but I think
>> you can also give the unit testing framework a flag that makes it abort
>> after the first error. In no way will the exception escape from the
>> unittest.main() call though, it is all caught and handled inside, also
>> by intention.
>>
>>
>>> But that's probably easy because we just need to catch exceptions for
>>> every method call, so it's not exactly the same thing..
>>
>> I don't understand what you want to say here. I also don't understand
>> what your problem in general is. I guess there are some expectations
>> which are not satisfied, but you haven't explained those explicitly yet.
>>
>
> I think Andrea wants to do the same thing but with nose and not
> unittest.
>
> Ramit
>
> This email is confidential and subject to important disclaimers and
> conditions including on offers for the purchase or sale of
> securities, accuracy and completeness of information, viruses,
> confidentiality, legal privilege, and legal entity disclaimers,
> available at http://www.jpmorgan.com/pages/disclosures/email.
>

Do what?  Like Ulrich Eckhart I simply don't understand what she's 
getting at.  Perhaps it's a problem with Englsh being a second language 
issue rather than Python itself.  Thankfully I'm sure that everything 
will come out in the wash.

-- 
Cheers.

Mark Lawrence.