These are the files that got modified in between. Revision 2994 has the matchers working.
Reversing to 2994 highlighted these files: [EMAIL PROTECTED]:~/Sites/xxx.local/xxx/rails/trunk/vendor/plugins/ rspec$ svn up -r 2995 D stories/example_groups/nested_groups D stories/resources/spec/nested_group_spec.rb U stories/resources/steps/running_rspec.rb Updated to revision 2995. [EMAIL PROTECTED]:~/Sites/xxx.local/xxx/rails/trunk/vendor/plugins/ rspec$ cd .. [EMAIL PROTECTED]:~/Sites/xxx.local/xxx/rails/trunk/vendor/plugins $ cd rspec_on_rails/ [EMAIL PROTECTED]:~/Sites/xxx.local/xxx/rails/trunk/vendor/plugins/ rspec_on_rails$ svn up -r 2995 At revision 2995. [EMAIL PROTECTED]:~/Sites/xxx.local/xxx/rails/trunk/vendor/plugins/ rspec_on_rails$ svn up -r 2994 U lib/spec/rails/version.rb A lib/spec/rails/example/behaviour/functional_example.rb A lib/spec/rails/example/behaviour/controller_example.rb U lib/spec/rails/example/behaviour/rails_example_group.rb A lib/spec/rails/example/behaviour/rails_example.rb A lib/spec/rails/example/behaviour/view_example.rb A lib/spec/rails/example/behaviour/helper_example.rb A lib/spec/rails/example/behaviour/model_example.rb Updated to revision 2994. [EMAIL PROTECTED]:~/Sites/xxx.local/xxx/rails/trunk/vendor/plugins/ rspec_on_rails$ cd ../rspec [EMAIL PROTECTED]:~/Sites/xxx.local/xxx/rails/trunk/vendor/plugins/ rspec$ svn up -r 2994 U stories/resources/test/test_case_with_should_methods.rb U stories/resources/test/spec_and_test_together.rb D lib/spec/interop/test/unit/testcase.rb A lib/spec/interop/test/unit/example_group.rb U lib/spec/interop/test.rb U lib/spec/version.rb U lib/spec.rb Updated to revision 2994. After svn-down-ing to 2994, be_nil works in my stories again. Hope this helps someone :-) Daniel On 26 Nov 2007, at 19:09 26 Nov 2007, Daniel Tenner wrote: > 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 >>> rspec-users@rubyforge.org >>> http://rubyforge.org/mailman/listinfo/rspec-users >>> >> _______________________________________________ >> rspec-users mailing list >> rspec-users@rubyforge.org >> http://rubyforge.org/mailman/listinfo/rspec-users > > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
