chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes
In Isolator 6.1.2, given an empty A() in DLL A and an empty B() in DLL B, with both A() and B() faked, calling A() then asserting B() was not called results in an exception on account of Isolator believing incorrectly that B() was called.

The repro, bug highlighted:

[ img ]

When empty A() is not called, Isolator believes correctly that B() was not called:

[ img ]

Further data on this bug:

[ img ]

This appears to be the same bug as the one reported in thread "Method Not Called But Verify Says Unexpectedly Called" http://forums.typemock.com/viewtopic.php?t=1933

Hanukkah wish list: A fix for this bug and Isolator++ 64-bit.

Thanks!
Neil
asked by (27.7k points)

3 Answers

0 votes
Thanks for the great repro, it really helped!

This bug is now fixed in version 6.2.1, available for download from our site http://typemock.com/download/
answered by (1.9k points)
0 votes
Good news:

For the repro I posted, the bug is fixed in 6.2.1:

[ img ]

Bad news:

The real unit test I am working with that failed incorrectly in 6.1.2 continues to fail incorrectly in 6.2.1.

The test fails incorrectly on WasNotCalled() when I fake the WasNotCalled() class last (sensitive class name redacted):

[ img ]

The test passes when I fake the WasNotCalled() class first:

[ img ]

Good luck getting to the bottom of this!
answered by (27.7k points)
0 votes
Yoel emailed me a build that fixes this issue. Thanks Yoel! I'm looking forward to a new release at https://www.typemock.com/download so I can upgrade all of our machines to a version with the fix.
answered by (27.7k points)
...