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/059656.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.pyStephen J. Turnbull turnbull at sk.tsukuba.ac.jp
Sun Jan 8 17:10:50 CET 2006
>>>>> "Fredrik" == Fredrik Lundh <fredrik at pythonware.com> writes:

    Fredrik> many test frameworks support "expected failures" for this
    Fredrik> purpose.  how hard would it be to add a

    Fredrik>     unittest.FailingTestCase

    Fredrik> class that runs a TestCase, catches any errors in it, and
    Fredrik> signals an error ("test foo passed unexpectedly") if it
    Fredrik> runs cleanly ?

One can do even better than that.  unittest.FailingTestCase should
(except possibly for platform dependencies) know _how_ the TestCase is
expected to fail.  You also want to know if the error changes.


-- 
Graduate School of Systems and Information Engineering   University of Tsukuba
http://turnbull.sk.tsukuba.ac.jp/        Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
        Economics of Information Communication and Computation Systems
          Experimental Economics, Microeconomic Theory, Game Theory
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