RR omits "unexpected method invocation" when stub exists

[trogdoro]

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", which is great. However, if I also have stub(A).b it doesn't. It could be argued that the "b(3)" call is no longer unexpected given the stub, but it would be helpful to provide a clue that b(3) was called instead of b(2), lest the developer be left on his own to track this down. Mocking one invocation to a method and stubbing out the rest seems like a common use case.

[btakita]

Thanks. I'll take a look at fixing this.

[btakita]

You can use stub(A).b.verbose to see the signature of the calls to the stub of b.

However, I can see some sort of instrumenting method would be useful.

Maybe something like:

track(A).b?