On Wednesday, April 25, 2012 at 4:59 PM, Eric Milford wrote: > On Apr 25, 11:52 am, David Chelimsky <[email protected] > (http://gmail.com)> wrote: > > On Wed, Apr 25, 2012 at 10:17 AM, Eric Milford > > > > <[email protected] (http://bustoutsolutions.com)> wrote: > > > I have a couple of specs that pass when run in isolation, but fail > > > when run w/ the entire test suite. The tests expect single > > > expectations that pass correctly when run alone, but I get an error > > > that the expectation was expected 1 time but received 2 times when run > > > w/ the entire test suite. The action around the expectation is > > > triggered in an after_create callback and there are other specs that > > > create models and therefore trigger this action. It seems that state > > > isn't being cleared correctly? Is there something I need to do to > > > resolve this or any suggestions? Thanks. > > > > > > > > > Gotta provide a bit more context. I can guess what might be going > > wrong, but we could end up going back and forth for quite a while. > > Please post one of the examples that fails intermittently, including > > any lets, befores, etc. And probably the after_create callback as > > well. > > > > Thanks, > > David > > > > >
> Here is an example of the failing specs... > > https://gist.github.com/4cc802291686a6f5bc46 > > The callback is in the model > > after_destroy { Notifier.notify_time_cancelled(self) } > > Thanks! Thanks for posting that. I put some questions/comments in the gist. -- You received this message because you are subscribed to the Google Groups "rspec" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rspec?hl=en.
