Chapter 2. Writing Tests for PHPUnit
how we can write tests using PHPUnit that exercise PHP's array operations.
The example introduces the basic conventions and steps for writing tests
with PHPUnit:
The tests for a class Class go into a class ClassTest.ClassTest inherits (most of the time) from PHPUnit_Framework_TestCase.The tests are public methods that are named test*.Alternatively, you can use the @test annotation in a method's docblock to mark it as a test method.Inside the test methods, assertion methods such as assertEquals() (see ) are used to assert that an actual value matches an expected value.Example 2.1: Testing array operations with PHPUnit&?php
class StackTest extends PHPUnit_Framework_TestCase
public function testPushAndPop()
$stack = array();
$this-&assertEquals(0, count($stack));
array_push($stack, 'foo');
$this-&assertEquals('foo', $stack[count($stack)-1]);
$this-&assertEquals(1, count($stack));
$this-&assertEquals('foo', array_pop($stack));
$this-&assertEquals(0, count($stack));
Whenever you are tempted to type something into a
print statement or a debugger expression, write it
as a test instead.
--Martin FowlerTest Dependencies
Unit Tests are primarily written as a good practice to help developers
identify and fix bugs, to refactor code and to serve as documentation
for a unit of software under test. To achieve these benefits, unit tests
ideally should cover all the possible paths in a program. One unit test
usually covers one specific path in one function or method. However a
test method is not necessary an encapsulated, independent entity. Often
there are implicit dependencies between test methods, hidden in the
implementation scenario of a test.
--Adrian Kuhn et. al.
PHPUnit supports the declaration of explicit dependencies between test
methods. Such dependencies do not define the order in which the test
methods are to be executed but they allow the returning of an instance of
the test fixture by a producer and passing it to the dependent consumers.
A producer is a test method that yields its unit under test as return value.A consumer is a test method that depends on one or more producers and their return values.
how to use the @depends annotation to express
dependencies between test methods.
Example 2.2: Using the @depends annotation to express dependencies&?php
class StackTest extends PHPUnit_Framework_TestCase
public function testEmpty()
$stack = array();
$this-&assertEmpty($stack);
* @depends testEmpty
public function testPush(array $stack)
array_push($stack, 'foo');
$this-&assertEquals('foo', $stack[count($stack)-1]);
$this-&assertNotEmpty($stack);
* @depends testPush
public function testPop(array $stack)
$this-&assertEquals('foo', array_pop($stack));
$this-&assertEmpty($stack);
In the example above, the first test, testEmpty(),
creates a new array and asserts that it is empty. The test then returns
the fixture as its result. The second test, testPush(),
depends on testEmpty() and is passed the result of that
depended-upon test as its argument. Finally, testPop()
depends upon testPush().
To quickly localize defects, we want our attention to be focussed on
relevant failing tests. This is why PHPUnit skips the execution of a test
when a depended-upon test has failed. This improves defect localization by
exploiting the dependencies between tests as shown in
Example 2.3: Exploiting the dependencies between tests&?php
class DependencyFailureTest extends PHPUnit_Framework_TestCase
public function testOne()
$this-&assertTrue(FALSE);
* @depends testOne
public function testTwo()
?&phpunit --verbose DependencyFailureTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 5.00Mb
There was 1 failure:
1) DependencyFailureTest::testOne
Failed asserting that false is true.
/home/sb/DependencyFailureTest.php:6
There was 1 skipped test:
1) DependencyFailureTest::testTwo
This test depends on "DependencyFailureTest::testOne" to pass.
Tests: 1, Assertions: 1, Failures: 1, Skipped: 1.
A test may have more than one @depends annotation.
PHPUnit does not change the order in which tests are executed, you have to
ensure that the dependencies of a test can actually be met before the test
A test that has more than one @depends annotation
will get a fixture from the first producer as the first argument, a fixture
from the second producer as the second argument, and so on.
Example 2.4: Test with multiple dependencies&?php
class MultipleDependenciesTest extends PHPUnit_Framework_TestCase
public function testProducerFirst()
$this-&assertTrue(true);
return 'first';
public function testProducerSecond()
$this-&assertTrue(true);
return 'second';
* @depends testProducerFirst
* @depends testProducerSecond
public function testConsumer()
$this-&assertEquals(
array('first', 'second'),
func_get_args()
?&phpunit --verbose MultipleDependenciesTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 3.25Mb
OK (3 tests, 3 assertions)Data Providers
A test method can accept arbitrary arguments. These arguments are to be
provided by a data provider method (additionProvider() in
The data provider method to be used is specified using the
@dataProvider annotation.
A data provider method must be public and either return
an array of arrays or an object that implements the Iterator
interface and yields an array for each iteration step. For each array that
is part of the collection the test method will be called with the contents
of the array as its arguments.
Example 2.5: Using a data provider that returns an array of arrays&?php
class DataTest extends PHPUnit_Framework_TestCase
* @dataProvider additionProvider
public function testAdd($a, $b, $expected)
$this-&assertEquals($expected, $a + $b);
public function additionProvider()
return array(
array(0, 0, 0),
array(0, 1, 1),
array(1, 0, 1),
array(1, 1, 3)
?&phpunit DataTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 5.75Mb
There was 1 failure:
1) DataTest::testAdd with data set #3 (1, 1, 3)
Failed asserting that 2 matches expected 3.
/home/sb/DataTest.php:9
Tests: 4, Assertions: 4, Failures: 1.Example 2.6: Using a data provider that returns an Iterator object&?php
require 'CsvFileIterator.php';
class DataTest extends PHPUnit_Framework_TestCase
* @dataProvider additionProvider
public function testAdd($a, $b, $expected)
$this-&assertEquals($expected, $a + $b);
public function additionProvider()
return new CsvFileIterator('data.csv');
?&phpunit DataTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 5.75Mb
There was 1 failure:
1) DataTest::testAdd with data set #3 ('1', '1', '3')
Failed asserting that 2 matches expected '3'.
/home/sb/DataTest.php:11
Tests: 4, Assertions: 4, Failures: 1.Example 2.7: The CsvFileIterator class&?php
class CsvFileIterator implements Iterator {
protected $
protected $key = 0;
protected $
public function __construct($file) {
$this-&file = fopen($file, 'r');
public function __destruct() {
fclose($this-&file);
public function rewind() {
rewind($this-&file);
$this-&current = fgetcsv($this-&file);
$this-&key = 0;
public function valid() {
return !feof($this-&file);
public function key() {
return $this-&
public function current() {
return $this-&
public function next() {
$this-&current = fgetcsv($this-&file);
$this-&key++;
When a test receives input from both a @dataProvider
method and from one or more tests it @depends on, the
arguments from the data provider will come before the ones from
depended-upon tests. The arguments from depended-upon tests will be the
same for each data set.
Example 2.8: Combination of @depends and @dataProvider in same test&?php
class DependencyAndDataProviderComboTest extends PHPUnit_Framework_TestCase
public function provider()
return array(array('provider1'), array('provider2'));
public function testProducerFirst()
$this-&assertTrue(true);
return 'first';
public function testProducerSecond()
$this-&assertTrue(true);
return 'second';
* @depends testProducerFirst
* @depends testProducerSecond
* @dataProvider provider
public function testConsumer()
$this-&assertEquals(
array('provider1', 'first', 'second'),
func_get_args()
?&phpunit --verbose DependencyAndDataProviderComboTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 3.50Mb
There was 1 failure:
1) DependencyAndDataProviderComboTest::testConsumer with data set #1 ('provider2')
Failed asserting that two arrays are equal.
--- Expected
+++ Actual
0 =& 'provider1'
0 =& 'provider2'
1 =& 'first'
2 =& 'second'
/home/sb/DependencyAndDataProviderComboTest.php:31
Tests: 4, Assertions: 4, Failures: 1.
Testing Exceptions
shows how to use the @expectedException annotation to
test whether an exception is thrown inside the tested code.
Example 2.9: Using the @expectedException annotation&?php
class ExceptionTest extends PHPUnit_Framework_TestCase
* @expectedException InvalidArgumentException
public function testException()
?&phpunit ExceptionTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 4.75Mb
There was 1 failure:
1) ExceptionTest::testException
Expected exception InvalidArgumentException
Tests: 1, Assertions: 1, Failures: 1.
Additionally, you can use @expectedExceptionMessage,
@expectedExceptionMessageRegExp and
@expectedExceptionCode in combination with
@expectedException to test the exception message and
exception code as shown in
Example 2.10:
Using the @expectedExceptionMessage,
@expectedExceptionMessageRegExp and
@expectedExceptionCode annotations
class ExceptionTest extends PHPUnit_Framework_TestCase
* @expectedException
InvalidArgumentException
* @expectedExceptionMessage Right Message
public function testExceptionHasRightMessage()
throw new InvalidArgumentException('Some Message', 10);
* @expectedException
InvalidArgumentException
* @expectedExceptionMessageRegExp #Right.*#
public function testExceptionMessageMatchesRegExp()
throw new InvalidArgumentException('Some Message', 10);
* @expectedException
InvalidArgumentException
* @expectedExceptionCode 20
public function testExceptionHasRightCode()
throw new InvalidArgumentException('Some Message', 10);
?&phpunit ExceptionTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 3.00Mb
There were 3 failures:
1) ExceptionTest::testExceptionHasRightMessage
Failed asserting that exception message 'Some Message' contains 'Right Message'.
2) ExceptionTest::testExceptionMessageMatchesRegExp
Failed asserting that exception message 'Some Message' matches '#Right.*#'.
3) ExceptionTest::testExceptionHasRightCode
Failed asserting that expected exception code 20 is equal to 10.
Tests: 3, Assertions: 6, Failures: 3.
More examples of @expectedExceptionMessage,
@expectedExceptionMessageRegExp and
@expectedExceptionCode are shown in
respectively.
Alternatively, you can use setExpectedException() or
setExpectedExceptionRegExp() to set the expected
exception as shown in .
Example 2.11: Expecting an exception to be raised by the tested code&?php
class ExceptionTest extends PHPUnit_Framework_TestCase
public function testException()
$this-&setExpectedException('InvalidArgumentException');
public function testExceptionHasRightMessage()
$this-&setExpectedException(
'InvalidArgumentException', 'Right Message'
throw new InvalidArgumentException('Some Message', 10);
public function testExceptionMessageMatchesRegExp()
$this-&setExpectedExceptionRegExp(
'InvalidArgumentException', '/Right.*/', 10
throw new InvalidArgumentException('The Wrong Message', 10);
public function testExceptionHasRightCode()
$this-&setExpectedException(
'InvalidArgumentException', 'Right Message', 20
throw new InvalidArgumentException('The Right Message', 10);
?&phpunit ExceptionTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 3.00Mb
There were 4 failures:
1) ExceptionTest::testException
Expected exception InvalidArgumentException
2) ExceptionTest::testExceptionHasRightMessage
Failed asserting that exception message 'Some Message' contains 'Right Message'.
3) ExceptionTest::testExceptionMessageMatchesRegExp
Failed asserting that exception message 'The Wrong Message' contains '/Right.*/'.
4) ExceptionTest::testExceptionHasRightCode
Failed asserting that expected exception code 20 is equal to 10.
Tests: 4, Assertions: 8, Failures: 4.
shows the methods provided for testing exceptions.
Table 2.1. Methods for testing exceptionsMethodMeaningvoid setExpectedException(string $exceptionName[, string $exceptionMessage = '', integer $exceptionCode = NULL])Set the expected $exceptionName, $exceptionMessage, and $exceptionCode.void setExpectedExceptionRegExp(string $exceptionName[, string $exceptionMessageRegExp = '', integer $exceptionCode = NULL])Set the expected $exceptionName, $exceptionMessageRegExp, and $exceptionCode.String getExpectedException()Return the name of the expected exception.
You can also use the approach shown in
to test exceptions.
Example 2.12: Alternative approach to testing exceptions&?php
class ExceptionTest extends PHPUnit_Framework_TestCase {
public function testException() {
// ... Code that is expected to raise an exception ...
catch (InvalidArgumentException $expected) {
$this-&fail('An expected exception has not been raised.');
If the code that is expected to raise an exception in
does not raise the expected exception, the subsequent call to
fail() will halt the test and signal a problem with the
test. If the expected exception is raised, the catch
block will be executed, and the test will end successfully.
Testing PHP Errors
By default, PHPUnit converts PHP errors, warnings, and notices that are
triggered during the execution of a test to an exception. Using these
exceptions, you can, for instance, expect a test to trigger a PHP error as
shown in .
Example 2.13: Expecting a PHP error using @expectedException&?php
class ExpectedErrorTest extends PHPUnit_Framework_TestCase
* @expectedException PHPUnit_Framework_Error
public function testFailingInclude()
include 'not_existing_file.php';
?&phpunit -d error_reporting=2 ExpectedErrorTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 5.25Mb
OK (1 test, 1 assertion)
PHPUnit_Framework_Error_Notice and
PHPUnit_Framework_Error_Warning represent PHP notices
and warnings, respectively.
When testing that relies on php functions that trigger errors like
fopen it can sometimes be useful to use error
suppression while testing. This allows you to check the return values by
suppressing notices that would lead to a phpunit
PHPUnit_Framework_Error_Notice.
Example 2.14: Testing return values of code that uses PHP Errors&?php
class ErrorSuppressionTest extends PHPUnit_Framework_TestCase
public function testFileWriting() {
$writer = new FileW
$this-&assertFalse(@$writer-&write('/is-not-writeable/file', 'stuff'));
class FileWriter
public function write($file, $content) {
$file = fopen($file, 'w');
if($file == false) {
?&phpunit ErrorSuppressionTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 1 seconds, Memory: 5.25Mb
OK (1 test, 1 assertion)
Without the error suppression the test would fail reporting
fopen(/is-not-writeable/file): failed to open stream:
No such file or directory.
Testing Output
Sometimes you want to assert that the execution of a method, for
instance, generates an expected output (via echo or
print, for example). The
PHPUnit_Framework_TestCase class uses PHP's
feature to provide the functionality that is
necessary for this.
shows how to use the expectOutputString() method to
set the expected output. If this expected output is not generated, the
test will be counted as a failure.
Example 2.15: Testing the output of a function or method&?php
class OutputTest extends PHPUnit_Framework_TestCase
public function testExpectFooActualFoo()
$this-&expectOutputString('foo');
print 'foo';
public function testExpectBarActualBaz()
$this-&expectOutputString('bar');
print 'baz';
?&phpunit OutputTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 5.75Mb
There was 1 failure:
1) OutputTest::testExpectBarActualBaz
Failed asserting that two strings are equal.
--- Expected
+++ Actual
Tests: 2, Assertions: 2, Failures: 1.
shows the methods provided for testing output
Table 2.2. Methods for testing outputMethodMeaningvoid expectOutputRegex(string $regularExpression)Set up the expectation that the output matches a $regularExpression.void expectOutputString(string $expectedString)Set up the expectation that the output is equal to an $expectedString.bool setOutputCallback(callable $callback)Sets up a callback that is used to, for instance, normalize the actual output.Error output
Whenever a test fails PHPUnit tries its best to provide you with as much
context as possible that can help to identify the problem.
Example 2.16: Error output generated when an array comparison fails&?php
class ArrayDiffTest extends PHPUnit_Framework_TestCase
public function testEquality() {
$this-&assertEquals(
array(1,2,3 ,4,5,6),
array(1,2,33,4,5,6)
?&phpunit ArrayDiffTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 5.25Mb
There was 1 failure:
1) ArrayDiffTest::testEquality
Failed asserting that two arrays are equal.
--- Expected
+++ Actual
/home/sb/ArrayDiffTest.php:7
Tests: 1, Assertions: 1, Failures: 1.
In this example only one of the array values differs and the other values
are shown to provide context on where the error occurred.
When the generated output would be long to read PHPUnit will split it up
and provide a few lines of context around every difference.
Example 2.17: Error output when an array comparison of an long array fails&?php
class LongArrayDiffTest extends PHPUnit_Framework_TestCase
public function testEquality() {
$this-&assertEquals(
array(0,0,0,0,0,0,0,0,0,0,0,0,1,2,3 ,4,5,6),
array(0,0,0,0,0,0,0,0,0,0,0,0,1,2,33,4,5,6)
?&phpunit LongArrayDiffTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 5.25Mb
There was 1 failure:
1) LongArrayDiffTest::testEquality
Failed asserting that two arrays are equal.
--- Expected
+++ Actual
/home/sb/LongArrayDiffTest.php:7
Tests: 1, Assertions: 1, Failures: 1.Edge cases
When a comparison fails PHPUnit creates textual representations of the
input values and compares those. Due to that implementation a diff
might show more problems than actually exist.
This only happens when using assertEquals or other 'weak' comparison
functions on arrays or objects.
Example 2.18: Edge case in the diff generation when using weak comparison&?php
class ArrayWeakComparisonTest extends PHPUnit_Framework_TestCase
public function testEquality() {
$this-&assertEquals(
,2,3 ,4,5,6),
array('1',2,33,4,5,6)
?&phpunit ArrayWeakComparisonTest
PHPUnit 4.6.0 by Sebastian Bergmann and contributors.
Time: 0 seconds, Memory: 5.25Mb
There was 1 failure:
1) ArrayWeakComparisonTest::testEquality
Failed asserting that two arrays are equal.
--- Expected
+++ Actual
/home/sb/ArrayWeakComparisonTest.php:7
Tests: 1, Assertions: 1, Failures: 1.
In this example the difference in the first index between
1 and '1' is
reported even though assertEquals considers the values as a match.为什么用fraps录制的游戏是断断续续的？_fraps吧_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：6,091贴子：
为什么用fraps录制的游戏是断断续续的？收藏
前几天才下了个fraps，但是录制的游戏断断续续，分成了n个视频啊。而且大多数视频都只是一秒钟，最长的只有29秒。我录的是avi格式的。不能录成一个整的视频吗？求指教。
1楼 23:13&|
在录像那里 把它改成
LOOP buffer length
它默认的是30
还有 请下载置顶里的那个FRAPS
那个是不用注册的
你在网上下的FRAPS是没有注册的只能录30秒
2楼 22:39&|
登录百度帐号
内&&容:使用签名档&&
为兴趣而生，贴吧更懂你。&或精品：open gl编程指南 buffer .webbuffer getbuffer loading buffer stringb..
扫扫二维码，随身浏览文档
手机或平板扫扫即可继续访问
openGLframebufferobject编程指南
举报该文档为侵权文档。
举报该文档含有违规或不良信息。
反馈该文档无法正常浏览。
举报该文档为重复文档。
推荐理由：
将文档分享至：
分享完整地址
文档地址：
粘贴到BBS或博客
flash地址：
支持嵌入FLASH地址的网站使用
html代码：
&embed src='/DocinViewer-4.swf' width='100%' height='600' type=application/x-shockwave-flash ALLOWFULLSCREEN='true' ALLOWSCRIPTACCESS='always'&&/embed&
450px*300px480px*400px650px*490px
支持嵌入HTML代码的网站使用
您的内容已经提交成功
您所提交的内容需要审核后才能发布，请您等待！
3秒自动关闭窗口