On Feb 8, 2011, at 4:14 AM, Matt W. wrote:
#page.current_path.should == sign_in_path
sign_in_path is one of the routes in my application and works fine
inside a describe/it block.
I don’t understand why the matcher recognises visit() but not
I’m surprised either of them do.
Actually, I’m not, but that’s because I know something that you don’t
know (because I wrote it and it’s not well documented):
A matcher created using the Matcher DSL is provided access to the
example it is running in. When it receives method_missing, it asks the
example if _it_ will respond to the message and, if so, sends it to the
If visit() is defined in the scope of the example using “def visit”,
then example.respond_to?(:visit) would return true, so the matcher would
send visit() to the example.
If, however, sign_in_path() is handled with method_missing(), but
respond_to?() is not also overridden to return true for
respond_to?(:sign_in_path), then the matcher would call super from
method_missing, raising the NameError.
You can test this theory out by putting the following in the same
example before the matcher:
If my guess is correct, the former will pass, but the latter will fail.
If they both pass, then I’m not sure about the explanation.
rspec-users mailing list