On Mon, Nov 1, 2010 at 10:32 AM, David Chelimsky <dchelim...@gmail.com> wrote: > > Can you post a real example of this complete with spec, > implementation, and failure message? > > Thx
I'm trying :)! So far it's been hard to isolate. Looks like many of the failures I get in my application actually happen "far away" from the original stub statement. So we stub the class method on one point of the spec file, and then on a subsequent unrelated context it gets called by some observer code. Due to the changes from 2753b492e, the message gets dispatched to ActiveRecord::Base instead of Settings. I'll try to reproduce this within rspec-rails' own specs. -- Bira http://compexplicita.wordpress.com http://compexplicita.tumblr.com _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
