From: Brian Candler <b.candler@...>
Date: 2009-03-30T04:51:33+09:00
Subject: Re: testy.rb - ruby testing that's mad at the world

Ara Howard wrote:
>        result.check :name, :expect => 42, :actual => ultimate.answer

I'm afraid I'm missing something. Why is this better than

  assert_equal 42, ultimate.answer, "name"
?

>    . testing should improve your code and help your users, not make
> you want to
>    kill yourself

Hear hear to that!

> requiring programmers learn exactly 2 new method calls

Well, it would be nice to know what those 2 methods calls were, and 
their semantics, without reverse-engineering the code. Are these 
Testy.testing and Result#check ?

I did find the gem, and installed it, but the generated rdoc is entirely 
free of comments or explanation.

The two samples don't really help me understand why testy is good or how 
to use it effectively, since they are both more verbose that what I 
would have written in test/unit to get the same result.

How would I do something equivalent to these?

   assert_raises(RuntimeError) { somecode }

   assert_match /error/i, response.body

I think I'd also miss the ability to have setup and teardown before each 
test (something which 'shoulda' makes very simple and effective).

Please don't get me wrong - I'm absolutely interested in something which 
will make testing simpler and easier, if I can understand how to use it 
effectively.

Regards,

Brian.
-- 
Posted via http://www.ruby-forum.com/.