[rspec-users] Latest update - broken be_matchers?
daniel.ruby at tenner.org
Mon Nov 26 14:09:26 EST 2007
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
I'd love to know what it was when someone figures it out though.
On 26 Nov 2007, at 18:27 26 Nov 2007, David Chelimsky wrote:
> On Nov 26, 2007 11:57 AM, Josh Knowles <joshknowles at gmail.com> wrote:
>> On 11/26/07, Daniel Tenner <daniel.ruby at tenner.org> 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.
>> Josh Knowles
>> phone: 509-979-1593
>> email: joshknowles at gmail.com
>> web: http://joshknowles.com
>> rspec-users mailing list
>> rspec-users at rubyforge.org
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users