A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2006-January/059526.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.py"Martin v. Löwis" martin at v.loewis.de
Sun Jan 8 19:01:20 CET 2006
Fred L. Drake, Jr. wrote:
> I like the way trial (from twisted) supports this.  The test method is written 
> normally, in whatever class makes sense.  Then the test is marked with an 
> attribute to say it isn't expected to pass yet.  When the code is fixed and 
> the test passes, you get that information in trial's output, and can unmark 
> the test.  This avoids having to refactor test classes just to update the 
> status of a test.

So how is the mark added? I would suggest

   @xfail
   def test_foo(self):
     self.assertEquals(0,1)

Regards,
Martin
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