First time I have a look inside the RSpec codebase (let alone the Story Runner), and not much luck this time. But, counter-intuitively enough, I think it's probably nothing to do with RailsStory itself since that didn't change in the last update. Trying to add an include Spec::Matchers in there also didn't help.
Couldn't quite figure it out though. Too much to absorb in a single sitting. I'd love to know what it was when someone figures it out though. Daniel On 26 Nov 2007, at 18:27 26 Nov 2007, David Chelimsky wrote: > On Nov 26, 2007 11:57 AM, Josh Knowles <[EMAIL PROTECTED]> wrote: >> On 11/26/07, Daniel Tenner <[EMAIL PROTECTED]> wrote: >>> Just seven upped the latest rspec update, and suddenly all my >>> be_matchers don't work anymore (they worked just before I updated): >> >> <snip /> >> >>> Anyone else getting that? >> >> All of my controller specs are passing, but my stories are failing >> with the same error. >> >> This works: >> response.success?.should == true >> >> This doesn't: >> response.should be_success > > Actually I'm surprised these were ever working as RailsStory doesn't > include Spec::Matchers - just Spec::Rails::Matchers. The matchers must > have been making their way in through the back door. > > I won't have time to look at this until tonight, but feel free to > submit a patch in the mean time if you can figure it out. > > Cheers, > David > >> >> -- >> Josh Knowles >> phone: 509-979-1593 >> email: [EMAIL PROTECTED] >> web: http://joshknowles.com >> >> _______________________________________________ >> rspec-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/rspec-users >> > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users _______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
