doug livesey
2009-Apr-08 18:08 UTC
[rspec-users] updated to latest gems, rspec not catching flash.now
Hi, after an update to all the latest gems, I have a controller spec failing that wasn''t previously: flash[:alert].should eql( "Blah blah." )** The flash is being set by "flash.now[:alert] = ''...''" in this instance. Can anyone suggest how I can make this work again? Cheers, Doug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090408/c962a7d3/attachment.html>
Zach Dennis
2009-Apr-08 21:21 UTC
[rspec-users] updated to latest gems, rspec not catching flash.now
On Wed, Apr 8, 2009 at 2:08 PM, doug livesey <biot023 at gmail.com> wrote:> Hi, after an update to all the latest gems, I have a controller spec failing > that wasn''t previously: > ?? flash[:alert].should eql( "Blah blah." ) > > The flash is being set by "flash.now[:alert] = ''...''" in this instance. > Can anyone suggest how I can make this work again?I just submitted a patch to ticket #11834 to resolve this issue in rspec-rails: https://rspec.lighthouseapp.com/projects/5645-rspec/tickets/98-11834-fake-controller-flash-object#ticket-98-9 In the mean time you can manually patch your local rspec-rails (if you unpack rspec and rspec-rails into vendor/gems or vendor/plugins this should work fine). Or you can do Xavier suggests on that ticket and add a few lines to your spec_helper, until rspec-rails is updated. HTH,> Cheers, > ?? Doug. > > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >-- Zach Dennis http://www.continuousthinking.com http://www.mutuallyhuman.com
doug livesey
2009-Apr-09 16:53 UTC
[rspec-users] updated to latest gems, rspec not catching flash.now
Didn''t spot this when you replied earlier -- cheers for that! Doug. 2009/4/8 Zach Dennis <zach.dennis at gmail.com>> On Wed, Apr 8, 2009 at 2:08 PM, doug livesey <biot023 at gmail.com> wrote: > > Hi, after an update to all the latest gems, I have a controller spec > failing > > that wasn''t previously: > > flash[:alert].should eql( "Blah blah." ) > > > > The flash is being set by "flash.now[:alert] = ''...''" in this instance. > > Can anyone suggest how I can make this work again? > > I just submitted a patch to ticket #11834 to resolve this issue in > rspec-rails: > > > https://rspec.lighthouseapp.com/projects/5645-rspec/tickets/98-11834-fake-controller-flash-object#ticket-98-9 > > In the mean time you can manually patch your local rspec-rails (if you > unpack rspec and rspec-rails into vendor/gems or vendor/plugins this > should work fine). Or you can do Xavier suggests on that ticket and > add a few lines to your spec_helper, until rspec-rails is updated. > > HTH, > > > > Cheers, > > Doug. > > > > _______________________________________________ > > rspec-users mailing list > > rspec-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/rspec-users > > > > > > -- > Zach Dennis > http://www.continuousthinking.com > http://www.mutuallyhuman.com > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090409/10ea4bbf/attachment.html>