blocks|key|223468|text|你的问题是你没有注入你的依赖(闭包)，这总是使单元测试变得更加困难，并且可能使隔离变得不可能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|223469|把闭包注入到SUT::foo()中，而不是在里面创建它，你会发现测试变得更容易了。|offset|length|style|CODE|223470|下面是我将如何设计该方法(请记住，我对您的真实代码一无所知，因此这对您来说可能实用，也可能不实用)：|223471|class+SUT+
{
++++public+function+foo($bar,+$someFunction)+
++++{
++++++++$bar->baz($someFunction);
++++}
}

class+SUTTest+extends+PHPUnit_Framework_TestCase+
{
++++public+function+testFoo()+
++++{
++++++++$someFunction+=+function()+{};

++++++++$mockBar+=+$this->getMockBuilder('Bar')
+++++++++++++->setMethods(array('baz'))
+++++++++++++->getMock();
++++++++$mockBar->expects($this->once())
+++++++++++++->method('baz')
+++++++++++++->with($someFunction);

++++++++$sut+=+new+SUT();

++++++++$sut->foo($mockBar,+$someFunction);
++++}
}|code-block|syntax|javascript|223472|entityMap^0|0|6|A|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|V|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Your problem is that you aren't injecting your dependency (the closure), which always makes unit testing harder, and can make isolation impossible.

Inject the closure into <code>SUT::foo()</code> instead of creating it inside there and you'll find testing much easier.

Here is how I would design the method (bearing in mind that I know nothing about your real code, so this may or may not be practical for you):

<pre><code>class SUT 
{
 public function foo($bar, $someFunction) 
 {
 $bar-&gt;baz($someFunction);
 }
}

class SUTTest extends PHPUnit_Framework_TestCase 
{
 public function testFoo() 
 {
 $someFunction = function() {};

 $mockBar = $this-&gt;getMockBuilder('Bar')
 -&gt;setMethods(array('baz'))
 -&gt;getMock();
 $mockBar-&gt;expects($this-&gt;once())
 -&gt;method('baz')
 -&gt;with($someFunction);

 $sut = new SUT();

 $sut-&gt;foo($mockBar, $someFunction);
 }
}
</code></pre>

blocks|key|6921|text|如果闭包在SUT中有一些副作用，可以通过模拟调用后的测试进行验证，那么可以使用returnCallback提供另一个要用传递的参数调用的闭包，并将其返回值返回给SUT。这将允许您调用SUT的闭包来引起副作用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|6922|+class+SUT+{
+++++public+function+foo($bar)+{
+++++++++$someFunction+=+function()+{+return+5+*+3;+};
+++++++++return+$bar->baz($someFunction);
+++++}
+}

+class+SUTTest+extends+PHPUnit_Framework_TestCase+{
+++++public+function+testFoo()+{
+++++++++$mockBar+=+$this->getMockBuilder('Bar')
++++++++++++++->setMethods(array('baz'))
++++++++++++++->getMock();
+++++++++$mockBar->expects($this->once())
++++++++++++++->method('baz')
++++++++++++++->will($this->returnCallback(function+($someFunction)+{
++++++++++++++++++return+$someFunction();
++++++++++++++}));

+++++++++$sut+=+new+SUT();

+++++++++self::assertEquals(15,+$sut->foo($mockBar));
+++++}
+}|code-block|syntax|javascript|6923|entityMap^0|5|3|13|E|28|3|2J|3|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|L|$]]

If the closure has some side effects inside <code>SUT</code> that could be verified by the test after the mock invocation, use <code>returnCallback</code> to provide another closure to be called with the passed arguments and have its return value returned to <code>SUT</code>. This will allow you to call <code>SUT</code>'s closure to cause the side effects.

<pre><code> class SUT {
 public function foo($bar) {
 $someFunction = function() { return 5 * 3; };
 return $bar-&gt;baz($someFunction);
 }
 }

 class SUTTest extends PHPUnit_Framework_TestCase {
 public function testFoo() {
 $mockBar = $this-&gt;getMockBuilder('Bar')
 -&gt;setMethods(array('baz'))
 -&gt;getMock();
 $mockBar-&gt;expects($this-&gt;once())
 -&gt;method('baz')
 -&gt;will($this-&gt;returnCallback(function ($someFunction) {
 return $someFunction();
 }));

 $sut = new SUT();

 self::assertEquals(15, $sut-&gt;foo($mockBar));
 }
 }
</code></pre>

blocks|key|6957|text|如果你想模拟一个匿名函数(回调)，你可以用__invoke方法模拟一个类。例如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|6958|$shouldBeCalled+=+$this->getMock(\stdClass::class,+['__invoke']);
$shouldBeCalled->expects($this->once())
++++->method('__invoke');

$someServiceYouAreTesting->testedMethod($shouldBeCalled);|code-block|syntax|javascript|6959|如果您使用的是最新的PHPUnit，则必须使用模拟构建器来完成此操作：|6960|$shouldBeCalled+=+$this->getMockBuilder(\stdClass::class)
++++->setMethods(['__invoke'])
++++->getMock();

$shouldBeCalled->expects($this->once())
++++->method('__invoke');

$someServiceYouAreTesting->testedMethod($shouldBeCalled);|6961|您还可以为方法参数设置期望或设置返回值，这与对任何其他方法执行此操作的方式相同：|6962|$shouldBeCalled->expects($this->once())
++++->method('__invoke')
++++->with($this->equalTo(5))
++++->willReturn(15);|6963|entityMap^0|L|8|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|10|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

If you want to mock an anonymous function (callback) you can mock a class with <code>__invoke</code> method. For example:

<pre><code>$shouldBeCalled = $this-&gt;getMock(\stdClass::class, ['__invoke']);
$shouldBeCalled-&gt;expects($this-&gt;once())
 -&gt;method('__invoke');

$someServiceYouAreTesting-&gt;testedMethod($shouldBeCalled);
</code></pre>

If you are using latest PHPUnit, you would have to use mock builder to do the trick:

<pre><code>$shouldBeCalled = $this-&gt;getMockBuilder(\stdClass::class)
 -&gt;setMethods(['__invoke'])
 -&gt;getMock();

$shouldBeCalled-&gt;expects($this-&gt;once())
 -&gt;method('__invoke');

$someServiceYouAreTesting-&gt;testedMethod($shouldBeCalled);
</code></pre>

You can also set expectations for method arguments or set a returning value, just the same way you would do it for any other method:

<pre><code>$shouldBeCalled-&gt;expects($this-&gt;once())
 -&gt;method('__invoke')
 -&gt;with($this-&gt;equalTo(5))
 -&gt;willReturn(15);
</code></pre>

This came up trying to write a test for a method of a class that calls a mock method with a closure. How would you verify the closure being called?

I know that you would be able to assert that the parameter is an instance of <code>Closure</code>. But how would you check anything about the closure?

For example how would you verify the function that is passed:

<pre><code> class SUT {
 public function foo($bar) {
 $someFunction = function() { echo "I am an anonymous function"; };
 $bar-&gt;baz($someFunction);
 }
 }

 class SUTTest extends PHPUnit_Framework_TestCase {
 public function testFoo() {
 $mockBar = $this-&gt;getMockBuilder('Bar')
 -&gt;setMethods(array('baz'))
 -&gt;getMock();
 $mockBar-&gt;expects($this-&gt;once())
 -&gt;method('baz')
 -&gt;with( /** WHAT WOULD I ASSERT HERE? **/);

 $sut = new SUT();

 $sut-&gt;foo($mockBar);
 }
 }
</code></pre>

You can't compare two closures in PHP. Is there a way in PHPUnit to execute the parameter passed in or in some way verify it?

PHPUnit testing with closures

单元测试

这是在尝试为调用带有闭包的模拟方法的类的方法编写测试时出现的。您将如何验证被调用的闭包？我知道您可以断言该参数是Closure的一个实例。但是你怎么检查闭包呢？例如，如何验证传递的函数： class SUT {     public function foo($bar) {         $someFunction ...

问使用闭包进行PHPUnit测试
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用闭包进行PHPUnit测试EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用闭包进行PHPUnit测试
EN