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.
On Wed, Apr 8, 2009 at 2:08 PM, doug livesey [email protected] 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
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users
–
Zach D.
http://www.continuousthinking.com
Technology Made for Humans by humans Data Analytics Data Analytics Data has become a critical part of business for most organizations. We work with you to ensure you have confidence in your data, can properly access it, and present it in a way that...
Est. reading time: 13 minutes
Didn’t spot this when you replied earlier – cheers for that!
Doug.
2009/4/8 Zach D. [email protected]