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
0 votes
I am running a unit test against a generic public method of a class that calls two private methods, one that is generic and one that is not. When the unit test goes to verify that the private methods have been called, it succeeds for the nongeneric method, but fails for the generic method.

I have debugged the unit test and stepped through the code. I can step right into the generic private method without any problem if I have the test set to use the original implementation. So, I know that the method is correctly being called, but when I call Isolate.Verify.NonPublic.WasCalled to verify that the method was called, I get the VerifyException that the method was expected but not called.

Am I missing something or is this a bug?

asked by bhunter (3.4k points)

1 Answer

0 votes
Hi Brian,

We reproduced this issue here with similar code to the one you described. This is indeed a bug.

Thanks for letting us know, we will fix it in the near future.

Best Regards,
Typemock Support
answered by Elisha (12k points)