2008/9/30 Yusuke ENDOH <mame / tsg.ne.jp>:
> Hi,
>
> 2008/9/30 Ryan Davis <ryand-ruby / zenspider.com>:
>> I always found the <obj> output to be harder to read...
>
> Hmm... Why?
>
> To be honest, when I glance test results, I hardly read any English
> messages :-)  I just search '<' at the line head mechanically.
>
> In addition, the <obj> output is helpful in terms of machine readablity.
>
>
>> and multiple lines harder to write processors
>
> Indeed, the current output of test/unit is harder to write processors.
> But I don't think the cause is multiple lines.  Appropriate line feeds
> will be rather helpful to parse if you parse as line-at-a-time.
>
>
>
>> PP is _really_really_ slow. too slow. By default miniunit should be as fast
>> as freakin' possible. That means inspect.
>
> But the current implementation will build message string only when its
> test is failed.  So it is not a problem, isn't it?
>
> # In addition, speed is very very week reason for ruby...
>
>
>> If and where it doesn't look good, the user has every option to override:
>>
>> class TestMyVeryComplexObject < Test::Unit::TestCase
>>  def mu_pp(obj)
>>    pretty_inspect(obj).gsub(/[\w\/\.]+:\d+/, 'FILE:LINE')
>>  end
>> end
>>
>> or... whatever the user wants.
>
> I want you to think that the users of miniunit is not only those who
> write tests but also those who only run tests.
> So it is important to switch mu_pp *without modifying test code*.
> The command-line option is needed at least, I think.
>
> --
> Yusuke ENDOH <mame / tsg.ne.jp>
>
>


I still look forward to hearing from you soon.

-- 
Yusuke ENDOH <mame / tsg.ne.jp>