Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Misleading report with argument constraints in message expectations #34
Shouldn't it report:
The thing was: when RSpec fails to match the arguments (3,2,2), it looks for similar argument expectations (i.e, with the same method), and the first it finds is (1,2,3), although :test has already been called with those arguments. Instead of this, it should take into account whether the method has already been called with those arguments.
I've fixed it in this commit, and moved the bug_report_34_spec into its proper place: