[Rails] Re: rspec issues
2008/11/2 [EMAIL PROTECTED] <[EMAIL PROTECTED]> > > b) makes sense, though it is surprising: I mean developer-defined > errors are usually Exceptions, and should be caught too, no ? I need > to pick up my ruby book again. > It's a common developer mistake to derive new exception classes from Exception, rather than StandardError. Such exception classes will not be rescued by a default rescue clause. -- James. http://blog.floehopper.org --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: rspec issues
b) makes sense, though it is surprising: I mean developer-defined errors are usually Exceptions, and should be caught too, no ? I need to pick up my ruby book again. Elise On Oct 31, 10:05 am, "James Mead" <[EMAIL PROTECTED]> wrote: > Hi Elise, > > 2008/10/31 [EMAIL PROTECTED] <[EMAIL PROTECTED]> > > > - mocking (ok, i'm using mocha, so maybe it isn't rspec): i make a > > mailer raise an error like this: > > DummyMailer.stubs(:deliver_invitation).raises(Exception) > > and in my code, surround this with begin ... rescue, the exception is > > not caught ! > > a) Are you sure deliver_invitation is being called? > b) Are you using just a default rescue clause? This will only rescue > StandardError's and descendants of StandardError. Exception is not a > descendant of StandardError. I think Mocha raises a StandardError by > default, so if you change your stubbing as follows, a default rescue clause > will work... > > DummyMailer.stubs(:deliver_invitation).raises > > If you are still seeing unexpected behaviour, come over to the Mocha mailing > list [1] and we'll see if we can help. > > -- > James.http://blog.floehopper.org > > [1]http://groups.google.com/group/mocha-developer --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: rspec issues
b) makes sense, though it is surprising: I mean developer-defined errors are usually Exceptions, and should be caught too, no ? I need to pick up my ruby book again. Elise On Oct 31, 10:05 am, "James Mead" <[EMAIL PROTECTED]> wrote: > Hi Elise, > > 2008/10/31 [EMAIL PROTECTED] <[EMAIL PROTECTED]> > > > - mocking (ok, i'm using mocha, so maybe it isn't rspec): i make a > > mailer raise an error like this: > > DummyMailer.stubs(:deliver_invitation).raises(Exception) > > and in my code, surround this with begin ... rescue, the exception is > > not caught ! > > a) Are you sure deliver_invitation is being called? > b) Are you using just a default rescue clause? This will only rescue > StandardError's and descendants of StandardError. Exception is not a > descendant of StandardError. I think Mocha raises a StandardError by > default, so if you change your stubbing as follows, a default rescue clause > will work... > > DummyMailer.stubs(:deliver_invitation).raises > > If you are still seeing unexpected behaviour, come over to the Mocha mailing > list [1] and we'll see if we can help. > > -- > James.http://blog.floehopper.org > > [1]http://groups.google.com/group/mocha-developer --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: rspec issues
> > expected "new", got "/Users/elise/Rails/myapp/app/views/user/profiles/
> > new.html.erb"
> > So it expects the full path. That can't be right ?
>
> nope, it expects new and gets the full path instead.
> what's your render command?
render :action => :new
> Typical ruby thing. "should be" tests for the two
> strings are an identical string object (one and the same thingy in
> memory)
> use:
> assigns['page'].menu.should eql("home alone")
OK, thanks
Elise
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---
[Rails] Re: rspec issues
> - render_template:
> response.should render_template('new')
> i get the following fail
> expected "new", got "/Users/elise/Rails/myapp/app/views/user/profiles/
> new.html.erb"
> So it expects the full path. That can't be right ?
nope, it expects new and gets the full path instead.
what's your render command?
> - should be: doesn't give me the result i expect for two strings that
> are equal.
> assigns['page'].menu.should be("home alone")
> gives me
> expected "home alone", got "home alone"
>
Typical ruby thing. "should be" tests for the two
strings are an identical string object (one and the same thingy in
memory)
use:
assigns['page'].menu.should eql("home alone")
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---
[Rails] Re: rspec issues
Hi Elise, 2008/10/31 [EMAIL PROTECTED] <[EMAIL PROTECTED]> > - mocking (ok, i'm using mocha, so maybe it isn't rspec): i make a > mailer raise an error like this: > DummyMailer.stubs(:deliver_invitation).raises(Exception) > and in my code, surround this with begin ... rescue, the exception is > not caught ! > a) Are you sure deliver_invitation is being called? b) Are you using just a default rescue clause? This will only rescue StandardError's and descendants of StandardError. Exception is not a descendant of StandardError. I think Mocha raises a StandardError by default, so if you change your stubbing as follows, a default rescue clause will work... DummyMailer.stubs(:deliver_invitation).raises If you are still seeing unexpected behaviour, come over to the Mocha mailing list [1] and we'll see if we can help. -- James. http://blog.floehopper.org [1] http://groups.google.com/group/mocha-developer --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
