You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have "mock(A).b(2)" and "A.b(3)" is invoked instead, RR clues me in on this by listing "b(3)" under "unexpected method invocation". However, if the code being tested has "rescue nil" after the line being stubbed, it doesn't. It appears from this that RR relies on your code allowing exceptions to float up to the top. RSpec must have another mechanism, since it was able to handle the same code (reporting the invalid call).
The text was updated successfully, but these errors were encountered:
If I have "mock(A).b(2)" and "A.b(3)" is invoked instead, RR clues me in on this by listing "b(3)" under "unexpected method invocation". However, if the code being tested has "rescue nil" after the line being stubbed, it doesn't. It appears from this that RR relies on your code allowing exceptions to float up to the top. RSpec must have another mechanism, since it was able to handle the same code (reporting the invalid call).
The text was updated successfully, but these errors were encountered: