[Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 (original) (raw)
Stephen J. Turnbull turnbull at sk.tsukuba.ac.jp
Sun Jan 8 17:10:50 CET 2006
- Previous message: [Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 - python/trunk/Lib/test/test_compiler.py
- Next message: [Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 - python/trunk/Lib/test/test_compiler.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"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
- Previous message: [Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 - python/trunk/Lib/test/test_compiler.py
- Next message: [Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 - python/trunk/Lib/test/test_compiler.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]