match function call prefer later mock.On

[egolearner]

Summary

Match function call prefer later mock.On.

Changes

Iterate backwardly in findExpectedCall/findClosestCall

Motivation

If there are multiple mock.On statement, it's natural to prefer later mock.On to earlier mock.On.

Related issues

Closes #1375

[egolearner]

From my point of view, it's natural to write the in the following way

mock.On(...)
doSthWithInterface().Expect(mock arg or mock return)

mock.On(...)
anotherDoSthWithInterface().Expect(mock arg or mock return)

instead of

mock.On(...)
mock.On(...)

doSthWithInterface().Expect(mock arg or mock return)
anotherDoSthWithInterface().Expect(mock arg or mock return)

However, this modification breaks a lot of tests. I need to know if this is the right direction to go.

[dolmen]

This is a breaking change. No way to have it accepted while maintaining compatibility.