Chapter 4. Writing Tests for PHPUnit

Example 4.1 shows how we have to rewrite our two tests from Example 1.4 so that we can use them with PHPUnit.

Example 4.1: Testing Array and sizeof() with PHPUnit

<?php
require_once 'PHPUnit/Framework.php';
 
class ArrayTest extends PHPUnit_Framework_TestCase
{
    public function testNewArrayIsEmpty()
    {
        // Create the Array fixture.
        $fixture = array();
 
        // Assert that the size of the Array fixture is 0.
        $this->assertEquals(0, sizeof($fixture));
    }
 
    public function testArrayContainsAnElement()
    {
        // Create the Array fixture.
        $fixture = array();
 
        // Add an element to the Array fixture.
        $fixture[] = 'Element';
 
        // Assert that the size of the Array fixture is 1.
        $this->assertEquals(1, sizeof($fixture));
    }
}
?>

	Whenever you are tempted to type something into a `print` statement or a debugger expression, write it as a test instead.
	--Martin Fowler

Example 4.1 shows the basic 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 expect no parameters and 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 Table 20.1) are used to assert that an actual value matches an expected value.

Note

Please note that in PHPUnit versions 2.0-2.3 the class names were prefixed with PHPUnit2_ instead of PHPUnit_. Existing test cases will still work with PHPUnit version 3.0, but it is highly recommended to update them to use the new class names.

1. Automating Tests

2. PHPUnit's Goals

3. Installing PHPUnit

4. Writing Tests for PHPUnit

5. The Command-Line Test Runner

6. Organizing Test Suites

7. Fixtures