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/059748.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.pyCollin Winter collinw at gmail.com
Sun Jan 15 12:00:53 CET 2006
On 1/13/06, Fredrik Lundh <fredrik at pythonware.com> wrote:
> my main nit is the name: the test isn't broken in itself, and doesn't need
> to be fixed; it's just not expected to succeed at this time.
>
> the usual term for this is "expected failure" (sometimes called XFAIL).
>
> for the developer, this means that a failure is not a regression, and is pro-
> bably not caused by something that the developer just did.

When I've implemented this kind of thing in the past, I've generally
called the decorator/marker/whatever "TODO" (or some variation of
caps/lowercase).

</bikeshed>

Thanks,
Collin Winter
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