=begin
One nice thing about Test::Unit output is that failures are justified making string comparisons easier.
In Test::Unit
<"minitest/unit is a small and fast replacement for ruby's huge and slow test/unit."> expected but was
<"minitest/unit is a small and fast replaecment for ruby's huge and slow test/unit.">.
In MiniTest::Unit
Expected "minitest/unit is a small and fast replacement for ruby's huge and slow test/unit.", not
"minitest/unit is a small and fast replaecment for ruby's huge and slow test/unit.".
The error (replaecment) is harder to find when the output is not justified.
FYI I submitted this as a feature request to Ryan Davis on the Rubyforge site and he rejected the request. I am resubmitting it here because I feel it is quite important and trivial to implement.
=end
|One nice thing about Test::Unit output is that failures are justified making string comparisons easier.
|
|In Test::Unit
|
|<"minitest/unit is a small and fast replacement for ruby's huge and slow test/unit."> expected but was
|<"minitest/unit is a small and fast replaecment for ruby's huge and slow test/unit.">.
|FYI I submitted this as a feature request to Ryan Davis on the Rubyforge site and he rejected the request. I am resubmitting it here because I feel it is quite important and trivial to implement.
Your proposal seems reasonable, but since Ryan rejected (and he is the
maintainer), he must have his own reason to reject. You have to
persuade Ryan anyway. Could you show us his reason to reject?
As an FYI, I decided to re-post the request here because a response Ryan made to a different ticket made me (apparently mistakenly) believe that Ruby was maintaining a separate fork of MiniTest. The conversation is here: