From: Jason Roelofs <jameskilton@...>
Date: 2007-07-13T21:37:17+09:00
Subject: Re: Unit testing exception types and messages

------=_Part_39123_5367789.1184330240144
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

e = assert_raise(RuntimeError) { my_code_that_raises }
assert_match(/Error message here/i, e.message)

Jason

On 7/13/07, gabriele renzi <rff_rffREMOVE@yahoo.it> wrote:
>
> On Fri, 13 Jul 2007 17:55:01 +0900, Dave Baldwin wrote:
>
> <snip>
> I do not think that there is a builtin assertion for exception
> messages, but defining your assert_raise_message is easy[1].
> But I thought I'd point out a small detail:
>
> > I can use an idiom like:
> >
> >       begin
> >               raise SomeExceptoin, "some message"
> >       rescue
> >               assert_equal("some message", $!.message)
> >               assert_raise(SomeExceptoin) {raise SomeExceptoin, "some
> message"}
> >       end
>
> this seem slightly wrong, wouldn't it be
>   begin
>     # raise SomeException with "some message"
>   rescue => e
>     assert_equal("some message", e.message)
>     assert_instance_of SomeException, e
>   end
> ?
> perlish variables are ugly and I think there is no need to raise the
> exception again.
>
>
> [1]
> even but I'd like to have a simple way to have filter_backtrace hide my
> own
> custom assertions
>
>
>
> --
> goto 10: http://www.goto10.it
> blog it: http://riffraff.blogsome.com
> blog en: http://www.riffraff.info
>
>

------=_Part_39123_5367789.1184330240144--