RetroSearch Browse

Sun Jan 8 19:09:27 CET 2006 · http://mail.python.org/pipermail/python-dev/2006-January/059527.html

On Jan 8, 2006, at 1:01 PM, Martin v. Löwis wrote:

> 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)

   def test_foo(self):
     self.assertEquals(0,1)
   test_foo.todo = "Why this test fails description message."

James

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

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

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