-
-
Notifications
You must be signed in to change notification settings - Fork 909
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set_flash[:foo].now matcher does not care if flash[:foo] really set .now #750
Comments
Hi @aried3r thanks for report. I worked at the master, that will be the 3.0.0, I am not sure if we will support 2.x after the 3.0.0 is released. But on master the problem was that when you call the So maybe the following code works on 2.8.0, I know that this works on 3.0.0 even before the PR.
@mcmire what you think about add this on the 3.0.0 milestone? |
It doesn't for me, sadly. I currently don't have the time to test this with the 3.0.0-rc version (with all the changes going on there), but I'd be glad to help you guys out next week. This gem helped me so much, I'd be glad to be of help. |
This might be an issue with 3.0, too, actually. I'm not going to let it hold up the release, though, as it's been in development forever and I'd rather get it out sooner rather than later. So I'll include a fix in the next release, but a PR is certainly still welcome. |
Closing this in favor of #755. |
I want to assert that a
flash.now[:foo]
uses.now
, but the test passes, even if.now
is not set.Code:
The reverse is not true, btw. If
flash.now[:foo]
is set in the controller but not in the spec, the test fails.Rails 4.2.3
Ruby 2.2.2
shoulda_matchers 2.8.0
The text was updated successfully, but these errors were encountered: