-
-
Notifications
You must be signed in to change notification settings - Fork 794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verify behavior change using DefaultValue.Mock 4.12.0 vs 4.13.0 #1024
Comments
Thanks for reporting. Looks like a bug. I'll take a look as soon as I find a free moment. |
This should be fixed in Moq version 4.14.2 (which has just become available on NuGet). Thanks again for reporting this regression, @DesrosiersC! |
Hi, Thanks @stakx for being so responsive! Moq is a great product and it is good to see it is so well maintained. |
Thanks for the kind feedback! ❤️ |
Hi, @stakx
The verify fails from version 4.14.0 and above. Thanks in advance for taking a look at this, |
@DesrosiersC — Thanks again for the report. I see, I wasn't quite thorough enough. Note to self, I suspect the problem lies (once again) here: Could be that the setup being added (the one for the auto-mocked return value) doesn't get marked as matched right away. |
I'm pretty newbie at Moq at all, so I may not have understood the problem, but this code I got to work: `using System; namespace MoqRegression
}` |
Thanks for your help @connywesth . |
@DesrosiersC, another fixed package version 4.14.3 should become available on NuGet shortly. Hopefully, this time it's fixed for real. 😃 If you find anything else amiss, please don't hesitate to report it. |
@stakx , thanks for taking the time to look at this. It is much appreciated. |
Hi,
I have a set of unit tests which start failing after upgrade from Moq 4.12.0 to 4.13.0.
Here's code which illustrates the issue:
The verify fails from version 4.1.13.0 and above.
Could you please let me know if the change of behavior is a bug and if I should wait for the fix.
Thanks,
Christian
The text was updated successfully, but these errors were encountered: