[Rspec-users] Mocking causes empty specification blocks
chrisjroos at gmail.com
Tue Jul 25 13:23:08 EDT 2006
On 7/25/06, David Chelimsky <dchelimsky at gmail.com> wrote:
> On 7/25/06, Chris Roos <chrisjroos at gmail.com> wrote:
> > Ahh, I couldn't previously find anyway of specifying that something
> > should not be called (I was trying should_not). I've just realised
> > that I need to do should_receive(:foo).never.
> > Not sure if it's possible but I'd guess the should_not_receive may be
> > more intuitive?
> I think you're right. Can you raise this as an issue at rubyforge?
Added as a feature request.
More information about the Rspec-users