[rspec-users] Failing to raise an exception in a stub
aslak.hellesoy at gmail.com
Thu Sep 13 16:29:42 EDT 2007
On 9/13/07, Jarkko Laine <jarkko at jlaine.net> wrote:
> I've come across rather strange behaviour when trying to raise an
> exception in a stubbed method.
> I'm speccing the behaviour of a Rails create action, where I'm using
> save! to catch failed saves. In the case of working save, I'm using
> the following stub:
> which works fine.
> However, in the negative case,
Passing a class only works if the new method takes 0 args. Otherwise
you have to pass an exception instance. ActiveRecord::RecordInvalid
> The save! call in the controller doesn't seem to work. I get the
> following error:
> ArgumentError in 'ClientsController POST /clients with invalid
> parameters should show new form again'
> wrong number of arguments (0 for 1)
> 41:in `create'
> The line #41 consists only of
> I'm at a loss seeing where the wrong number of arguments is really
> happening because save! certainly shouldn't assume any args.
> Moreover, both cases work fine in the real app, so it seems to me
> something funky is happening when stubbing the method.
> Anyone else stumbled upon anything similar?
> Jarkko Laine
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users