對於PHPUnit測試私有屬性和方法的功能分析

這篇文章主要介紹了PHPUnit測試私有屬性和方法功能,結合實例形式較為詳細的分析了使用PHPUnit針對私有屬性和方法進行測試的相關操作技巧與注意事項,需要的朋友可以參考下

本文實例講述了PHPUnit測試私有屬性和方法功能。分享給大家供大家參考，具體如下：

一、測試類別中的私有方法：

##

class Sample
{
  private $a = 0;
  private function run()
  {
    echo $a;
  }
}

class testSample()
{
    $method = new ReflectionMethod('Sample', 'run');
    $method->setAccessible(true); //将run方法从private变成类似于public的权限
    $method->invoke(new Sample()); //调用run方法
}

private static function run()
{
  echo 'run is a private static function';
}

那麼invoke函數還可以這麼寫：

$method->invoke(null); //只有静态方法可以不必传类的实例化

#如果run還需要傳參，例如：

private function run($x, $y)
{
  return $x + $y;
}

那麼，測試程式碼可以改為：

$method->invokeArgs(new Sample(), array(1, 2));
//array中依次写入要传的参数。执行结果返回3

【注意】：利用反射的方法測試私有方法雖好，但setAccessible函數是php5.3.2版本以後才支援的（>=5.3.2）

二、私有屬性的get/set#說完了私有方法，再來看看私有屬性，依舊拿Sample類別作為例子，想要取得或設定Sample類別中的私有屬性$a的值可以用以下方法：

public function testPrivateProperty()
{
  $reflectedClass = new ReflectionClass('Sample');
  $reflectedProperty = $reflectedClass->getProperty('a');
  $reflectedProperty->setAccessible(true);
  $reflectedProperty->getValue(); //获取$a的值
  $reflectedProperty->setValue(123); //给$a赋值:$a = 123;
}

上述方法對靜態屬性仍然有效。

到此，是不是瞬間感覺測試私有方法或屬性變得很容易了。

附：PHPunit 測試私有方法（英文原文）This article is part of a series on testing untestable code:

Testing private methods
Testing code that uses singletons
Stubbing static methods
• #Stubbing static methods

One question I get over and over again when talking about Unit Testing is this:

"How do I test the private attributes and methods of my objects?"

Lets assume we have a class Foo:

<?php
class Foo
{
  private $bar = &#39;baz&#39;;
  public function doSomething()
  {
    return $this->bar = $this->doSomethingPrivate();
  }
  private function doSomethingPrivate()
  {
    return &#39;blah&#39;;
  }
}
?>

<?php
class FooTest extends PHPUnit_Framework_TestCase
{
  /**
   * @covers Foo::doSomething
   * @covers Foo::doSomethingPrivate
   */
  public function testDoSomething()
  {
    $foo = new Foo;
    $this->assertEquals(&#39;blah&#39;, $foo->doSomething());
  }
}
?>

The test above

#

<?php
class FooTest extends PHPUnit_Framework_TestCase
{
  public function testPrivateAttribute()
  {
    $this->assertAttributeEquals(
     &#39;baz&#39;, /* expected value */
     &#39;bar&#39;, /* attribute name */
     new Foo /* object     */
    );
  }
}
?>

##1 testDoSomething() only works correctly whentestDoSomethingPrivate() works correctly. This means that we have indirectly testedtestDoSomethingPrivate(). The problem with this approach is that when the test fails we do not know directly where the root cause for the failure is. It could be in eithertestDoSomething() or testDoSomethingPrivate(). This makes the test less valuable.

PHPUnit supports reading protected and private attributes through thePHPUnit_Framework_Assert::readAttribute quals() exist to express assertions onprotected and private attributes:

<?php
class FooTest extends PHPUnit_Framework_TestCase
{
  /**
   * @covers Foo::doSomethingPrivate
   */
  public function testPrivateMethod()
  {
    $method = new ReflectionMethod(
     &#39;Foo&#39;, &#39;doSomethingPrivate&#39;
    );
    $method->setAccessible(TRUE);
    $this->assertEquals(
     &#39;blah&#39;, $method->invoke(new Foo)
    );
  }
}
?>

PHP 5.3.2 introduces the ReflectionMethod::setAccessible() method to allow the invocation of protected and private methods through the Reflmethod to allow the invocation of protected and private methods through the Reflmethod to allow the invocation of protected and private methods through the Reflmethod to allow the invocation of protected and private methods through the Reflmethod to allow the invocation of protected and private methods through the Reflmethod to allow the invocation of protected and private methods through the Reflmethod to allow API:

In the test above we directly test testDoSomethingPrivate(). When it fails we immediately know where to look for the root cause.

"In general, you don't want to break any encapsulation for the sake of testing ( or as Mom used to say, "don't expose your privates!"). Most of the time, you should be able to test a class by exercising its public methods. If there is significant functionality that private methods. , that might be a warning sign that there's another class in there struggling to get out."

PHP和redis實作悲觀鎖定機制的解析

#php中可變函數的使用總結

以上是對於PHPUnit測試私有屬性和方法的功能分析的詳細內容。更多資訊請關注PHP中文網其他相關文章！