I have some specs that run just fine using "rake spec:controllers" or "script/spec spec/controllers" but if I run "script/spec spec/controllers -X" with the spec server running, I end up getting some mocks that fail saying expected once, and being called twice. Any ideas what would cause this kind of behavior? It kind of gives cause to not trust my specs. Which one is correct? The one that is successful, or the one that is failing?
On Oct 24, 2007, at 9:03 PM, Steve wrote:> I have some specs that run just fine using "rake spec:controllers" or > "script/spec spec/controllers" but if I run "script/spec spec/ > controllers > -X" with the spec server running, I end up getting some mocks that > fail > saying expected once, and being called twice. Any ideas what would > cause > this kind of behavior? It kind of gives cause to not trust my > specs. Which > one is correct? The one that is successful, or the one that is > failing? >Did you try restarting the drb server? Scott
On Wed, 24 Oct 2007 21:36:15 -0400, Scott Taylor wrote:> > Did you try restarting the drb server? > > ScottYes. Multiple times. Exact same results each time.
On Oct 24, 2007, at 9:53 PM, Steve wrote:> On Wed, 24 Oct 2007 21:36:15 -0400, Scott Taylor wrote: >> >> Did you try restarting the drb server? >> >> Scott > > Yes. Multiple times. Exact same results each time.Well, I guess you''ll probably need to give us the following: What versions of the following: Ruby, OS, Rails, Rspec (if on trunk, have you run script/generate rspec recently?), anything else relevant... pastie of the specs + code You''ll probably want to open an issue in the tracker with this information (unless someone can point out the problem pretty quickly). Scott