Re: [rspec-users] no should raise_exception

raise_error already catches any type of exception, error or not:   class BlahException < Exception; end   class BlahError < StandardError; end lambda { raise BlahException }.should raise_error(BlahException) lambda { raise BlahError }.should raise_error(BlahError) lambda { raise "blah" }.sh

[rspec-users] no should raise_exception

I know there's a raise_error however...exceptions are not always errors, so I had expected a raise_exception matcher...would this be a reasonable addition (I'd be happy to do it). Thanks. -r ___ rspec-users mailing list rspec-users@rubyforge.org http://ru

Re: [rspec-users] State-based expectations (as per jMock in GOOS)

On 18 Dec 2009, at 14:46, Tom Stuart wrote: > Can you elaborate? From a position of no knowledge, the most obvious question > to me is: why would I care about the state of O? Either the change in O's > state is observable through its behaviour (in which case I specify that > behaviour) or it's