blocks|key|1198070|text|您可以使用Mock.Callback-方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1198071|var+mock+=+new+Mock<Handler>();
SomeResponse+result+=+null;
mock.Setup(h+=>+h.AsyncHandle(It.IsAny<SomeResponse>()))
++++.Callback<SomeResponse>(r+=>+result+=+r);

//+do+your+test
new+Foo(mock.Object).Bar(22);
Assert.NotNull(result);|code-block|syntax|javascript|1198072|如果你只想在传入的参数上检查一些简单的东西，你也可以直接这样做：|1198073|mock.Setup(h+=>+h.AsyncHandle(It.Is<SomeResponse>(response+=>+response+!=+null)));|1198074|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You can use the Mock.Callback-method:
<pre><code>var mock = new Mock&lt;Handler&gt;();
SomeResponse result = null;
mock.Setup(h =&gt; h.AsyncHandle(It.IsAny&lt;SomeResponse&gt;()))
 .Callback&lt;SomeResponse&gt;(r =&gt; result = r);

// do your test
new Foo(mock.Object).Bar(22);
Assert.NotNull(result);
</code></pre>
If you only want to check something simple on the passed in argument, you also can do it directly:
<pre><code>mock.Setup(h =&gt; h.AsyncHandle(It.Is&lt;SomeResponse&gt;(response =&gt; response != null)));
</code></pre>

blocks|key|1198100|text|Gamlor的答案是有效的，但另一种方法(我认为在测试中更具表现力)是……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1198101|var+mock+=+new+Mock<Handler>();
var+desiredParam+=+47;+//+this+is+what+you+want+to+be+passed+to+AsyncHandle
new+Foo(mock.Object).Bar(22);
mock.Verify(h+=>+h.AsyncHandle(desiredParam),+Times.Once());|code-block|syntax|javascript|1198102|Verify非常强大，值得花时间去适应。|1198103|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Gamlor's answer works, but another way of doing it (and one which I consider to be more expressive in the test) is...

<pre><code>var mock = new Mock&lt;Handler&gt;();
var desiredParam = 47; // this is what you want to be passed to AsyncHandle
new Foo(mock.Object).Bar(22);
mock.Verify(h =&gt; h.AsyncHandle(desiredParam), Times.Once());
</code></pre>

Verify is very powerful, and worth taking the time to get used to.

blocks|key|983609|text|你可以使用It.Is<TValue>()匹配器。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|983610|var+mock+=+new+Mock<Handler>();
new+Foo(mock.Object).Bar(22);
mock.Verify(h+=>+h.AsyncHandle(It.Is<SomeResponse>(r+=>+r+!=+null+)));|code-block|syntax|javascript|983611|entityMap^0|5|F|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

You could use <code>It.Is&lt;TValue&gt;()</code> matcher.

<pre><code>var mock = new Mock&lt;Handler&gt;();
new Foo(mock.Object).Bar(22);
mock.Verify(h =&gt; h.AsyncHandle(It.Is&lt;SomeResponse&gt;(r =&gt; r != null )));
</code></pre>

blocks|key|983668|text|Gamlor的回答对我很有效，但我想我会对John+Carpenter的评论进行扩展，因为我正在寻找一个涉及多个参数的解决方案。我想其他偶然发现这个页面的人可能也有类似的情况。我在Moq+documentation里找到了这个信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|983669|我将使用Gamlor的示例，但假设AsyncHandle方法有两个参数:一个string和一个SomeResponse对象。|style|CODE|983670|var+mock+=+new+Mock<Handler>();
string+stringResult+=+string.Empty;
SomeResponse+someResponse+=+null;
mock.Setup(h+=>+h.AsyncHandle(It.IsAny<string>(),+It.IsAny<SomeResponse>()))
++++.Callback<string,+SomeResponse>((s,+r)+=>+
++++{
++++++++stringResult+=+s;
++++++++someResponse+=+r;
++++});

//+do+your+test
new+Foo(mock.Object).Bar(22);
Assert.AreEqual("expected+string",+stringResult);
Assert.IsNotNull(someResponse);|code-block|syntax|javascript|983671|基本上，您只需要添加另一个具有适当类型的It.IsAny<>()，向Callback方法添加另一个类型，并根据需要更改lambda表达式。|983672|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Moq/moq4/wiki/Quickstart^0|2I|H|0|0|12|6|1B|C|0|0|K|C|Y|8|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@$A|11|B|12|F|G]|$A|13|B|14|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|15|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|16|8|@$A|17|B|18|F|G]|$A|19|B|1A|F|G]]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

Gamlor's answer worked for me, but I thought I would expand on John Carpenter's comment because I was looking for a solution involving more than one parameter. I figured other folks who stumble onto this page may be in a similar situation. I found this info in the <a href="https://github.com/Moq/moq4/wiki/Quickstart" rel="noreferrer">Moq documentation</a>.

I'll use Gamlor's example, but let's pretend the AsyncHandle method takes two arguments: a <code>string</code> and a <code>SomeResponse</code> object.

<pre><code>var mock = new Mock&lt;Handler&gt;();
string stringResult = string.Empty;
SomeResponse someResponse = null;
mock.Setup(h =&gt; h.AsyncHandle(It.IsAny&lt;string&gt;(), It.IsAny&lt;SomeResponse&gt;()))
 .Callback&lt;string, SomeResponse&gt;((s, r) =&gt; 
 {
 stringResult = s;
 someResponse = r;
 });

// do your test
new Foo(mock.Object).Bar(22);
Assert.AreEqual("expected string", stringResult);
Assert.IsNotNull(someResponse);
</code></pre>

Basically you just need to add another <code>It.IsAny&lt;&gt;()</code> with the appropriate type, add another type to the <code>Callback</code> method, and change the lambda expression as appropriate.

blocks|key|1198266|text|回调方法肯定会起作用，但如果你是在一个有很多参数的方法上做这件事，它可能会有点冗长。这是我用来删除一些样板文件的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1198267|var+mock+=+new+Mock<Handler>();

//+do+your+test+++
new+Foo(mock.Object).Bar(22);

var+arg+=+new+ArgumentCaptor<SomeResponse>();
mock.Verify(h+=>+h.AsyncHandle(arg.Capture()));
Assert.NotNull(arg.Value);|code-block|syntax|javascript|1198268|以下是ArgumentCaptor的源代码：|1198269|public+class+ArgumentCaptor<T>
{
++++public+T+Capture()
++++{
++++++++return+It.Is<T>(t+=>+SaveValue(t));
++++}

++++private+bool+SaveValue(T+t)
++++{
++++++++Value+=+t;
++++++++return+true;
++++}

++++public+T+Value+{+get;+private+set;+}
}|1198270|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

The Callback method will certainly work, but if you are doing this on a method with a lot of parameters it can be a bit verbose. Here is something that I have used to remove some of the boilerplate.

<pre><code>var mock = new Mock&lt;Handler&gt;();

// do your test 
new Foo(mock.Object).Bar(22);

var arg = new ArgumentCaptor&lt;SomeResponse&gt;();
mock.Verify(h =&gt; h.AsyncHandle(arg.Capture()));
Assert.NotNull(arg.Value);
</code></pre>

Here is the source for ArgumentCaptor:

<pre><code>public class ArgumentCaptor&lt;T&gt;
{
 public T Capture()
 {
 return It.Is&lt;T&gt;(t =&gt; SaveValue(t));
 }

 private bool SaveValue(T t)
 {
 Value = t;
 return true;
 }

 public T Value { get; private set; }
}
</code></pre>

blocks|key|983761|text|这也是可行的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|983762|Mock<InterfaceThing>+mockedObject+=+new+Mock<InterfaceThing>();
var+objectParameter+=+mockedObject.Invocations[1].Arguments[0]+as+ObjectParameter;|code-block|syntax|javascript|983763|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This also works: 

<pre><code>Mock&lt;InterfaceThing&gt; mockedObject = new Mock&lt;InterfaceThing&gt;();
var objectParameter = mockedObject.Invocations[1].Arguments[0] as ObjectParameter;
</code></pre>

blocks|key|1198323|text|另一种选择是使用Capture.In，它是Moq中的一个开箱即用的功能，允许您将参数捕获到集合中：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1198324|//Arrange
var+args+=+new+List<SomeResponse>();
mock.Setup(h+=>+h.AsyncHandle(Capture.In(args)));

//Act
new+Foo(mock.Object).Bar(22);

//Assert
//...+assert+args.Single()+or+args.First()|code-block|syntax|javascript|1198325|entityMap^0|8|A|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

An alternative is to use <code>Capture.In</code>, which is an out-of-the-box feature in Moq that lets you capture arguments into a collection:
<pre class="lang-cs prettyprint-override"><code>//Arrange
var args = new List&lt;SomeResponse&gt;();
mock.Setup(h =&gt; h.AsyncHandle(Capture.In(args)));

//Act
new Foo(mock.Object).Bar(22);

//Assert
//... assert args.Single() or args.First()
</code></pre>

blocks|key|1198425|text|这里有很多好的答案！使用开箱即用的Moq功能集，直到您需要对传递给依赖项的几个类参数进行断言。但是，如果您最终遇到这种情况，带有It.Is匹配器的Moq+Verify特性并不能很好地隔离测试失败，而且捕获参数的返回/回调方式会向您的测试中添加不必要的代码行(对于我来说，长时间的测试是行不通的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1198426|这里有一个要点:我写了一个带有Moq+(4.12)扩展的https://gist.github.com/Jacob-McKay/8b8d41ebb9565f5fca23654fd944ac6b，它提供了一种更具声明性的方式来对传递给mock的参数进行断言，而没有上述缺点。下面是Verify部分现在的样子：|offset|length|1198427|++++++++mockDependency
++++++++++++.CheckMethodWasCalledOnce(nameof(IExampleDependency.PersistThings))
++++++++++++.WithArg<InThing2>(inThing2+=>
++++++++++++{
++++++++++++++++Assert.Equal("Input+Data+with+Important+additional+data",+inThing2.Prop1);
++++++++++++++++Assert.Equal("I+need+a+trim",+inThing2.Prop2);
++++++++++++})
++++++++++++.AndArg<InThing3>(inThing3+=>
++++++++++++{
++++++++++++++++Assert.Equal("Important+Default+Value",+inThing3.Prop1);
++++++++++++++++Assert.Equal("I+NEED+TO+BE+UPPER+CASED",+inThing3.Prop2);
++++++++++++});|code-block|syntax|javascript|1198428|如果Moq提供了一个功能来完成同样的事情，同时作为声明式的，并提供它所做的失败隔离，我会很兴奋的。祈祷吧！|1198429|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/Jacob-McKay/8b8d41ebb9565f5fca23654fd944ac6b^0|0|S|1W|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Lot's of good answers here! Go with the out of the box Moq feature-set until you need to make assertions about several class parameters passed to your dependencies. If you end up in that situation though, the Moq Verify feature with It.Is matchers doesn't do a good job of isolating the test failure, and the Returns/Callback way of capturing arguments adds unnecessary lines of code to your test (and long tests are a no-go for me).

Here is a gist: <a href="https://gist.github.com/Jacob-McKay/8b8d41ebb9565f5fca23654fd944ac6b" rel="nofollow noreferrer">https://gist.github.com/Jacob-McKay/8b8d41ebb9565f5fca23654fd944ac6b</a> with a Moq (4.12) extension I wrote that gives a more declarative way to make assertions about arguments passed to mocks, without the drawbacks aforementioned. Here is what the Verify section looks like now:

<pre><code> mockDependency
 .CheckMethodWasCalledOnce(nameof(IExampleDependency.PersistThings))
 .WithArg&lt;InThing2&gt;(inThing2 =&gt;
 {
 Assert.Equal("Input Data with Important additional data", inThing2.Prop1);
 Assert.Equal("I need a trim", inThing2.Prop2);
 })
 .AndArg&lt;InThing3&gt;(inThing3 =&gt;
 {
 Assert.Equal("Important Default Value", inThing3.Prop1);
 Assert.Equal("I NEED TO BE UPPER CASED", inThing3.Prop2);
 });
</code></pre>

I would be stoked if Moq provided a feature that accomplished the same thing while being as declarative and providing the failure isolation this does. Fingers crossed!

Imagine this class

<pre><code>public class Foo {

 private Handler _h;

 public Foo(Handler h)
 {
 _h = h;
 }

 public void Bar(int i)
 {
 _h.AsyncHandle(CalcOn(i));
 }

 private SomeResponse CalcOn(int i)
 {
 ...;
 }
}
</code></pre>

Mo(q)cking Handler in a test of Foo, how would I be able to check what <code>Bar()</code> has passed to <code>_h.AsyncHandle</code>?

Moq: How to get to a parameter passed to a method of a mocked service

想象一下这个类public class Foo {    private Handler _h;    public Foo(Handler h)    {        _h = h;    }    public void Bar(int i)    {        _h.AsyncHandle(CalcOn(i...

问Moq:如何获取传递给模拟服务的方法的参数
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Moq:如何获取传递给模拟服务的方法的参数EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Moq:如何获取传递给模拟服务的方法的参数
EN