A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-January/059534.html below:

[Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940

[Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 - python/trunk/Lib/test/test_compiler.py [Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 - python/trunk/Lib/test/test_compiler.pyNeal Norwitz nnorwitz at gmail.com
Sun Jan 8 22:47:12 CET 2006
On 1/8/06, Fredrik Lundh <fredrik at pythonware.com> wrote:
>
> many test frameworks support "expected failures" for this purpose.
> how hard would it be to add a
>
>     unittest.FailingTestCase
>
> class that runs a TestCase, catches any errors in it, and signals an
> error ("test foo passed unexpectedly") if it runs cleanly ?

http://python.org/sf/1399935
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4