Hello, this is probably not the right place for this discussion but I need someone who can point me in the right direction. Is there a general chat group or forums for unit testing and mocking in C#? I have a few questions regarding the design of the application in regards to mocking.
Hey, I've been trying to use Moq with IL2CPP backend (of Unity) and it's apparently not possible due to the nature of IL2CPP.
Since then, I've found Moq version 5 which supposedly no longer uses "Reflection.Emit". Which could mean that using Moq compiled with IL2CPP would be possible.
But after bumping Moq to version 5, I still see a similar issue where Reflection.Emit is used. Am I missing something?
Since then, I've found Moq version 5 which supposedly no longer uses "Reflection.Emit". Which could mean that using Moq compiled with IL2CPP would be possible.
But after bumping Moq to version 5, I still see a similar issue where Reflection.Emit is used. Am I missing something?
Yes, that's the goal. It's work in progress, though, with sporadic jolts of progress as I find time and energy to do it. With the advent of Roslyn-based SourceGenerators, I'm almost sure that that particular feature (compile-time proxy generation) will require the very latest VS that will ship with that)
I currently have a feature branch that extends the current analyzer feature to do the same, but it doesn't perform very well with large solutions
Ohh. I was using moq4 which after finishing some tests, I realised it did not support IL2CPP, then I read the docs from moq5 and got hopeful to have it working. Unfortunately I will need to come up with a different solution that supports AOT. Regarding the VS requirement, I believe that might be lifted by adding the required microsoft dlls as dependency.
Thanks a lot for your attention and reply. Keep up the amazing work.
Thanks a lot for your attention and reply. Keep up the amazing work.
Hello, I'm a web dev that just started on game dev. Trying to install Moq on unity running under ubuntu.
So far no luck, downloading and pasting the release dir inside Plugins did nothing useful, can't install via Visual Studio and I ran out of ideas. How do I install Moq to use in ubuntu/unity? Thanks
So far no luck, downloading and pasting the release dir inside Plugins did nothing useful, can't install via Visual Studio and I ran out of ideas. How do I install Moq to use in ubuntu/unity? Thanks
I went as far as downloading the source and putting it inside my project, but there was some code that could not be processed in linux
Hello everyone,
I'm trying to verify a mock that involves access to an indexer (
For some reason, it's reported that the underlying SUT is accessing
Why is that, and how can I overcome this?
Thanks
I'm trying to verify a mock that involves access to an indexer (
Microsoft.Extensions.Configuration.IConfiguration)For some reason, it's reported that the underlying SUT is accessing
IConfiguration.Item when I call configurationMock.VerifyNoOtherCalls().Why is that, and how can I overcome this?
Thanks
best way to troubleshoot that is to create a strict mock, it will throw at the call-site that performs that call @weitzhandler
Hi. I'm attempting to use It.Is<> outside of Setup but it seems to be returning null - I assume due to relying on knowing the current method. I was trying to add some code to remove boilerplate where the only thing changing is an argument (and condition expression) to a method call. Something like:
var mockCommandBus = new Mock<ICommandBus>();
mockCommandBus
.Setup(_ => _.PublishAsync(
testCommand,
It.IsAny<CancellationToken>()))
.ReturnsAsync(result);
return (mockCommandBus.Object, mockCommandBus);Called:
CommandBusBuilder.BuildMockCommandCall(
It.Is<RegisterNewApplication>(_ => _.Name == name && _.Description == description),
Result.Ok(new ApplicationId(id)));
In my head it makes sense on paper, but evidently due to how the argument is resolved and expression evaluated, it sort of needs to be inside
Setup. Anyone got any thoughts on this? Alternatives? I'm trying to avoid constantly writing the first block.
@RaringCoder With Moq 4,
It.Is and other matchers only work when used inside LINQ expression tree. What's important is their identity, so to speak, and that is only preserved in a LINQ expression tree. Once evaluated, that is gone and all ypu're left with is their retuen value, which is in fact completely irrelevant & ignored by Moq.
So if you want to avoid boilerplate you'd likely have to create a helper function (possibly parameterized) that creates similar setup/verify expressions for you as a whole. Extracting parts of an expression, then putting them back in somewhere else, means you have to go through the static
Expression.* factory methods which is going to be a pain in the b*tt compared to the C# compiler doing that for you automagically.
@trampster, Moq 4 doesn't (and probably cannot) fully support
Span<T> and other by-ref-like types due to limitations in .NET Reflection and LINQ expression trees. No way around it unfortunately.
There is a Docs folder, but it has very little in it and what is there is confusing and 2 years old.
There also doesn't appear to be a nuget package for it
Also there has only been one commit to it this year and that was in Feb
The readme itself lists the nuget package feed:
> CI package feed: http://kzu.nuget.cloud/index.json (CDN) or https://kzu.blob.core.windows.net/nuget/index.json (blob).
> CI package feed: http://kzu.nuget.cloud/index.json (CDN) or https://kzu.blob.core.windows.net/nuget/index.json (blob).
but unfortunately that simply doesn't perform well for large API surfaces :disappointed:
I tried optimizing it as much as possible using asp.net core but I don't think it's acceptable. So, source generators it is :smile:
(well, will be, just need to find time... but I've been already playing quite a bit with those, so I got a good grasp of what it will take)
Hi all, sorry if this is not the right place for questions like this - please redirect me.
I am updating a solution with around 10,000 tests from Moq 4.7.8 to Moq 4.14.5 and have most issues ironed (<50 failures I can attribute to the upgrade now) out but am stumped by odd behavior with Mock.As<T> where an object implements multiple interfaces and those interfaces define the same property. After setting the property, the object retains the old property value when casted to at least one of the interface versions and each time I correct the failing one, the previously successful one now fails. I am not sure that the changes in the changelog really describe the differences I am seeing.
Is there someone who can help me understand what changed with Mock.As<T> , and help me understand the correct pattern for setting up my mock so the property behaves as intended?
I am updating a solution with around 10,000 tests from Moq 4.7.8 to Moq 4.14.5 and have most issues ironed (<50 failures I can attribute to the upgrade now) out but am stumped by odd behavior with Mock.As<T> where an object implements multiple interfaces and those interfaces define the same property. After setting the property, the object retains the old property value when casted to at least one of the interface versions and each time I correct the failing one, the previously successful one now fails. I am not sure that the changes in the changelog really describe the differences I am seeing.
Is there someone who can help me understand what changed with Mock.As<T> , and help me understand the correct pattern for setting up my mock so the property behaves as intended?
@bluechrism it might help if we had a minimal code example to look at. Can you e.g. boil down one of your failing tests to just two or three interfaces with only one property each, then state your expectatipns (probably whatever would've happened with version 4.7), what happened instead (using the latest version), and why you think that isn't right? If so please post an issue over at https://github.com/moq/moq4.
Hey, before i write up another issue (and a full repro is coming for the other one), can someone explain this difference between new Mock<T> and using Mock.Of<T> with Mock.Get to set up a property: Again, both the Tests would pass with Mock 4.7.8 but the second now fails with 4.14.5.
@bluechrism Looking at the code base 4.14.5 used to setup the mock using the method SetupAllProperties which effectively setup stubs. That means that you would have a real get\set for all the properties. You can avoid that by using MockBehavior.Strict. The only question is why these tests are passing on 4.7.8, seems they should fail there as well...