Oops, I accidentally hit Reply instead of Reply to All...<br><br><div class="gmail_quote">On Wed, Sep 28, 2011 at 1:05 PM, Michael Foord <span dir="ltr"><<a href="mailto:fuzzyman@voidspace.org.uk">fuzzyman@voidspace.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#FFFFFF" text="#000000"><div class="im">
On 27/09/2011 19:59, Laurens Van Houtven wrote:
<blockquote type="cite">Sure, you just *do* it. The only advantage I see in
assertNotRaises is that when that exception is raised, you should
(and would) get a failure, not an error.<br>
</blockquote></div>
There are some who don't see the distinction between a failure and
an error as a useful distinction... I'm becoming more sympathetic to
that view.<br></div></blockquote><div><br><p>I agree. Maybe if there were less failures posing as errors and
errors posing as failures, I'd consider taking the distinction
seriously.</p>
<p>The only use case I've personally encountered is with fuzzy tests.
The example that comes to mind is one where we had a fairly complex
iterative algorithm for learning things from huge amounts of test data
and there were certain criteria (goodness of result, time taken) that
had to be satisfied. In that case, "it blew up because someone messed up
dependencies" and "it took 3% longer than is allowable" are pretty
obviously different... Considering how exotic that use case is, like I
said, I'm not really convinced how generally useful it is :) especially
since this isn't even a unit test...</p><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div bgcolor="#FFFFFF" text="#000000">
All the best,<br>
<br>
Michael<br></div></blockquote><div><br>cheers<br>lvh <br></div></div>