Mocks with the same verifiable invocation setup multiple times

const m = Mock.ofInstance(a => { });
m.setup(x => x(It.isValue(0))).returns(() => 0).verifiable();
m.setup(x => x(It.isValue(0))).returns(() => 0).verifiable();
m.object(0);
m.object(0);

m.verifyAll();

This fails with Verify Exception: Expected invocation on the mock 2 times, invoked 1 times. Is this not a supported scenario? I have a test where I set up several invocations, and a couple of them end up with the same expected signature. Is it expected that I only register each one once, then verify that it was called the correct number of times?

[deneboulton]

Hi, would you be able to verify if multiple registered setups work with Mock.ofType<Interface> when the matcher is exactly the same, please? From the docs and the above example I expected that it would.

I have code that looks like this:

const mock = TypeMoq.Mock.ofType<MyInterface>();
// setup for first call
mock
    .setup(f => f.funcThatReturnsPromise())
    .returns(() => Promise.resolve(valueA));
// setup for second call
mock
    .setup(f => f.funcThatReturnsPromise())
    .returns(() => Promise.resolve(valueB));

What happens is that the second setup trumps the first; so the first call receives valueB but the second call receives undefined. I found it interesting that all subsequent calls after the first return undefined and not valueB - though naturally both of those outcomes are undesirable as we want callA -> valueA & callB -> valueB. I would only expected undefined to be returned after the second call.

If I remove the second setup then all calls to funcThatReturnsPromise returns valueA as expected.

Previously this test setup code differed in that the setups were both different because funcThatReturnsPromise was receiving an argument, so:

mock
    .setup(f => f.funcThatReturnsPromise(inputA))
    .returns(() => Promise.resolve(valueA));
mock
    .setup(f => f.funcThatReturnsPromise(inputB))
    .returns(() => Promise.resolve(valueB));

This worked fine, so a call using inputA returned valueA and so on.

Any help would be much appreciated, thanks.

[florinn]

I guess it does make more sense to replay them in the order they were recorded. I’ve made the necessary changes.

Typemoq ver 0.1.1 is available and it includes these changes.

Please give it a try and let me know if you have any comments.